Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52a517c20912ecb38ae71af697cc5dda3f234b2a3723771e116b8f8188a5a243

Tx prefix hash: 347daf3d1cf9753f561d86f1b7fa4ca3d3a81a785e421e570608d7faf04c3a6a
Tx public key: 8ed4dde52d1c64b993fa3294f9eab3bf0cb6f5402d3f6e6459d9c8cf8ae09809
Timestamp: 1709947420 Timestamp [UCT]: 2024-03-09 01:23:40 Age [y:d:h:m:s]: 01:245:15:41:33
Block: 974221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434282 RingCT/type: yes/0
Extra: 018ed4dde52d1c64b993fa3294f9eab3bf0cb6f5402d3f6e6459d9c8cf8ae098090211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600080000000 dcy

stealth address amount amount idx
00: ecde68d481204bfc901131bda69b3088efb6eced744c439e471a123f93a8dc30 0.600080000000 1434174 of 0

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": 974231, "vin": [ { "gen": { "height": 974221 } } ], "vout": [ { "amount": 600080000, "target": { "key": "ecde68d481204bfc901131bda69b3088efb6eced744c439e471a123f93a8dc30" } } ], "extra": [ 1, 142, 212, 221, 229, 45, 28, 100, 185, 147, 250, 50, 148, 249, 234, 179, 191, 12, 182, 245, 64, 45, 63, 110, 100, 89, 217, 200, 207, 138, 224, 152, 9, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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