Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31631a6d41035964a47cae47677b3e2d1039fbf18a47a45de0697a0163aff1d1

Tx prefix hash: a3d973744e616a335e9091d831ed49dc1a60868fc66811c6e463d61bfbd939e7
Tx public key: 8e8e4738d988fc21c6193b8170261fd5eae867f2cf97c62728bf97af0b07ed00
Timestamp: 1721218170 Timestamp [UCT]: 2024-07-17 12:09:30 Age [y:d:h:m:s]: 00:175:17:45:59
Block: 1067671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125730 RingCT/type: yes/0
Extra: 018e8e4738d988fc21c6193b8170261fd5eae867f2cf97c62728bf97af0b07ed0002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f077a8ed95af0212fd53cd760cab53f36e0a4afe4fd94003b5ed31f93b7f135 0.600000000000 1538542 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": 1067681, "vin": [ { "gen": { "height": 1067671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f077a8ed95af0212fd53cd760cab53f36e0a4afe4fd94003b5ed31f93b7f135" } } ], "extra": [ 1, 142, 142, 71, 56, 217, 136, 252, 33, 198, 25, 59, 129, 112, 38, 31, 213, 234, 232, 103, 242, 207, 151, 198, 39, 40, 191, 151, 175, 11, 7, 237, 0, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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