Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec9ed276b6dc236cde41a4517140c8ec32f921bcbc50c558950d12a3c89c745

Tx prefix hash: 83840191074a1dde773a4124ed3835d45d9f751c2e1a5e56f64e6b0f6516b4c5
Tx public key: 452108eb4bea1d01e08a0fb14f41cc568982cf0ace0c4d68a4828e099b89962a
Timestamp: 1721623569 Timestamp [UCT]: 2024-07-22 04:46:09 Age [y:d:h:m:s]: 00:171:17:11:59
Block: 1071006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122875 RingCT/type: yes/0
Extra: 01452108eb4bea1d01e08a0fb14f41cc568982cf0ace0c4d68a4828e099b89962a02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e867790e48f534dde655c6adb69ddbcf4eec9774bf4a665f116b13dcf890da0 0.600000000000 1543069 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": 1071016, "vin": [ { "gen": { "height": 1071006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e867790e48f534dde655c6adb69ddbcf4eec9774bf4a665f116b13dcf890da0" } } ], "extra": [ 1, 69, 33, 8, 235, 75, 234, 29, 1, 224, 138, 15, 177, 79, 65, 204, 86, 137, 130, 207, 10, 206, 12, 77, 104, 164, 130, 142, 9, 155, 137, 150, 42, 2, 17, 0, 0, 0, 17, 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