Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e255aa627dc59f7daf578a61de7c7e0c4b5a93d85c38450aa62df54d29776d

Tx prefix hash: a8799583ade9331c8865f4ab91aca06c97a19b51e3e83939512cdc953d7c3a8b
Tx public key: fbe326fc7554af887c1ec5def94ea6f1758fae43447f209938a1d48fc8829861
Timestamp: 1740517336 Timestamp [UCT]: 2025-02-25 21:02:16 Age [y:d:h:m:s]: 00:339:20:59:59
Block: 1227194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240581 RingCT/type: yes/0
Extra: 01fbe326fc7554af887c1ec5def94ea6f1758fae43447f209938a1d48fc8829861021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 355c18b8c01018672ffd2317bcbdb6de17e7d7ae3d9dc4a6831d7f4db281d154 0.600000000000 1714067 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": 1227204, "vin": [ { "gen": { "height": 1227194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "355c18b8c01018672ffd2317bcbdb6de17e7d7ae3d9dc4a6831d7f4db281d154" } } ], "extra": [ 1, 251, 227, 38, 252, 117, 84, 175, 136, 124, 30, 197, 222, 249, 78, 166, 241, 117, 143, 174, 67, 68, 127, 32, 153, 56, 161, 212, 143, 200, 130, 152, 97, 2, 17, 0, 0, 0, 8, 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