Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4794b3972b53e0848474231a883b82df0585fafb8bb1a19c06b3fb64e65392b3

Tx prefix hash: 2dfaca0ffa26131391e1affbb0974497c129f3328b6e9c34b53aff7f244b2291
Tx public key: cefb28e51a4ffeb44e55d63dfb712fc3d525ee8a9bb10fc7a4a983d0079cee31
Timestamp: 1711544279 Timestamp [UCT]: 2024-03-27 12:57:59 Age [y:d:h:m:s]: 01:251:04:11:10
Block: 987476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438215 RingCT/type: yes/0
Extra: 01cefb28e51a4ffeb44e55d63dfb712fc3d525ee8a9bb10fc7a4a983d0079cee3102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4670eb43102c6312720e43d08dce39d91f38a0fd4d792977032d5f41ba83821 0.600000000000 1447727 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": 987486, "vin": [ { "gen": { "height": 987476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4670eb43102c6312720e43d08dce39d91f38a0fd4d792977032d5f41ba83821" } } ], "extra": [ 1, 206, 251, 40, 229, 26, 79, 254, 180, 78, 85, 214, 61, 251, 113, 47, 195, 213, 37, 238, 138, 155, 177, 15, 199, 164, 169, 131, 208, 7, 156, 238, 49, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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