Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19f600d27aef034bbdc5a63b3c7d9b1a699881fd6a467a46081a4e742fcba751

Tx prefix hash: 1876f2c82af5524d4812611b7fad9056a2a0ab4885daed8fc714146e3fa0ebfd
Tx public key: 0834f097b961eeb4f209cd8a961d79e36d4954fb5b0f4b14c8d52e29b1bfd513
Timestamp: 1751080382 Timestamp [UCT]: 2025-06-28 03:13:02 Age [y:d:h:m:s]: 00:141:16:15:21
Block: 1314244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99339 RingCT/type: yes/0
Extra: 010834f097b961eeb4f209cd8a961d79e36d4954fb5b0f4b14c8d52e29b1bfd51302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5fcf81e5ed062f09a0b4f3e865ce303bb9d8be1172b75062f435ee430afb17 0.600000000000 1801889 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": 1314254, "vin": [ { "gen": { "height": 1314244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5fcf81e5ed062f09a0b4f3e865ce303bb9d8be1172b75062f435ee430afb17" } } ], "extra": [ 1, 8, 52, 240, 151, 185, 97, 238, 180, 242, 9, 205, 138, 150, 29, 121, 227, 109, 73, 84, 251, 91, 15, 75, 20, 200, 213, 46, 41, 177, 191, 213, 19, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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