Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21c3e5f2305f2c36738834c9272bef56fada06163d96ed4970a646d4201b7832

Tx prefix hash: ff3f81d1c66a1cb1e14f2fa3c2b5e5f89174111d3e8125d4b96b97dd438c7e6c
Tx public key: e8ec482ed1ae20f93932af801a25d6f018a9d96d3010682ad71188f22c0400e2
Timestamp: 1746540621 Timestamp [UCT]: 2025-05-06 14:10:21 Age [y:d:h:m:s]: 00:199:02:45:21
Block: 1277070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140009 RingCT/type: yes/0
Extra: 01e8ec482ed1ae20f93932af801a25d6f018a9d96d3010682ad71188f22c0400e202110000000c1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb6bee62e3789b33c01d9b78c7fbe3d67f15b438ce637af526580fdf1ac21ee 0.600000000000 1764421 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": 1277080, "vin": [ { "gen": { "height": 1277070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb6bee62e3789b33c01d9b78c7fbe3d67f15b438ce637af526580fdf1ac21ee" } } ], "extra": [ 1, 232, 236, 72, 46, 209, 174, 32, 249, 57, 50, 175, 128, 26, 37, 214, 240, 24, 169, 217, 109, 48, 16, 104, 42, 215, 17, 136, 242, 44, 4, 0, 226, 2, 17, 0, 0, 0, 12, 31, 144, 81, 122, 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