Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab876ded460b2e52c61c174fc5fb9dc8fcc01e32c61ddefc40f80ea1b8bc1a18

Tx prefix hash: 9c671d5448189d9663af56d42fc472c1ccd530cf2019f7fb61f3e9b924817c1a
Tx public key: f4d80d74a91155ff4b676ee70f4420a7f04e89dcac19305b06f2d47f571f7245
Timestamp: 1700419956 Timestamp [UCT]: 2023-11-19 18:52:36 Age [y:d:h:m:s]: 01:145:12:38:49
Block: 895228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365186 RingCT/type: yes/0
Extra: 01f4d80d74a91155ff4b676ee70f4420a7f04e89dcac19305b06f2d47f571f724502110000000575e3f0e9000000000000000000

1 output(s) for total of 0.663342769000 dcy

stealth address amount amount idx
00: 4d45853b71673879da58ca1489a759e720fc5f8ef955be2031cf59f2727cea9e 0.663342769000 1351457 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": 895238, "vin": [ { "gen": { "height": 895228 } } ], "vout": [ { "amount": 663342769, "target": { "key": "4d45853b71673879da58ca1489a759e720fc5f8ef955be2031cf59f2727cea9e" } } ], "extra": [ 1, 244, 216, 13, 116, 169, 17, 85, 255, 75, 103, 110, 231, 15, 68, 32, 167, 240, 78, 137, 220, 172, 25, 48, 91, 6, 242, 212, 127, 87, 31, 114, 69, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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