Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2946d9cbfe69e042715c29b0c362e15a796b928264779df475c7d146144b385d

Tx prefix hash: 73b020cbef92d42e2fad70a3ed955dcd4916ba4d2ba7357bba7ce96855fc1695
Tx public key: d7beed9f46842f78ba32450c629df7c17621f242d8e8d2646ab58758f6d0c53a
Timestamp: 1712591349 Timestamp [UCT]: 2024-04-08 15:49:09 Age [y:d:h:m:s]: 00:322:20:16:03
Block: 996097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230823 RingCT/type: yes/0
Extra: 01d7beed9f46842f78ba32450c629df7c17621f242d8e8d2646ab58758f6d0c53a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7a83beaadbde44b1c80a9bb31b0086d8add325e20cc8769aa848cef6c1b51e 0.600000000000 1456513 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": 996107, "vin": [ { "gen": { "height": 996097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7a83beaadbde44b1c80a9bb31b0086d8add325e20cc8769aa848cef6c1b51e" } } ], "extra": [ 1, 215, 190, 237, 159, 70, 132, 47, 120, 186, 50, 69, 12, 98, 157, 247, 193, 118, 33, 242, 66, 216, 232, 210, 100, 106, 181, 135, 88, 246, 208, 197, 58, 2, 17, 0, 0, 0, 1, 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