Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e05d7d67a9b719d8ba51395802cfcb7e691de29012e704ba3fd8331d9dac8a

Tx prefix hash: 7fcf1a62ffd2f3bc351d82ad95a9993fc0e89523adb8c2b851c0871af08375a1
Tx public key: 5cb6a6adbb8619570c9a0f00bacaf689a842ea8403616037774bd02a91d9af5e
Timestamp: 1576643227 Timestamp [UCT]: 2019-12-18 04:27:07 Age [y:d:h:m:s]: 05:144:19:22:11
Block: 28102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251391 RingCT/type: yes/0
Extra: 015cb6a6adbb8619570c9a0f00bacaf689a842ea8403616037774bd02a91d9af5e02110000001fad433a0b000000000000000000

1 output(s) for total of 495.321607126000 dcy

stealth address amount amount idx
00: 38ff8fe05b0c1a548dab7c6b3127f9bc4eec5ae71df2a02e7e5c6f44027e6c90 495.321607126000 46624 of 0

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": 28112, "vin": [ { "gen": { "height": 28102 } } ], "vout": [ { "amount": 495321607126, "target": { "key": "38ff8fe05b0c1a548dab7c6b3127f9bc4eec5ae71df2a02e7e5c6f44027e6c90" } } ], "extra": [ 1, 92, 182, 166, 173, 187, 134, 25, 87, 12, 154, 15, 0, 186, 202, 246, 137, 168, 66, 234, 132, 3, 97, 96, 55, 119, 75, 208, 42, 145, 217, 175, 94, 2, 17, 0, 0, 0, 31, 173, 67, 58, 11, 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