Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 637c1f5de58e689a1a9945540b93b883ff924897e46cb54b6e1ec3de95f189c3

Tx prefix hash: 313f7c6d1ce26206a7c8d9d51be54a21d1921900f810add5d4fc742dacfb5f1a
Tx public key: 15bb4ca08adbd0b4e8cc9a989f1cbe33801362b4ebd7421e1233ad66401f67b7
Timestamp: 1731934500 Timestamp [UCT]: 2024-11-18 12:55:00 Age [y:d:h:m:s]: 00:132:13:24:34
Block: 1156400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94557 RingCT/type: yes/0
Extra: 0115bb4ca08adbd0b4e8cc9a989f1cbe33801362b4ebd7421e1233ad66401f67b7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c44fc60c250add406a0e264cef128b56cafaaa4d2b64504fda4e07dafa33503 0.600000000000 1642023 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1156410, "vin": [ { "gen": { "height": 1156400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c44fc60c250add406a0e264cef128b56cafaaa4d2b64504fda4e07dafa33503" } } ], "extra": [ 1, 21, 187, 76, 160, 138, 219, 208, 180, 232, 204, 154, 152, 159, 28, 190, 51, 128, 19, 98, 180, 235, 215, 66, 30, 18, 51, 173, 102, 64, 31, 103, 183, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8