Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30579489e91713d7e39a8459ef0f6456e2f540a172977424978b3995e057de1c

Tx prefix hash: 04d5af8d85c8ba16c9ada7f86732421ab80281728353e2b86a341c01b0e83ff3
Tx public key: 6c99cd9520969b1f5310ad9f2e92f42e0862fe04f62a789c4e23df8f5370ef7a
Timestamp: 1724445753 Timestamp [UCT]: 2024-08-23 20:42:33 Age [y:d:h:m:s]: 00:230:05:11:27
Block: 1094433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164382 RingCT/type: yes/0
Extra: 016c99cd9520969b1f5310ad9f2e92f42e0862fe04f62a789c4e23df8f5370ef7a02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cf43c7f713047f67ab2fc8588b26fc9d3a810e1b34118fae43ad679bbdd88e5 0.600000000000 1569550 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": 1094443, "vin": [ { "gen": { "height": 1094433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cf43c7f713047f67ab2fc8588b26fc9d3a810e1b34118fae43ad679bbdd88e5" } } ], "extra": [ 1, 108, 153, 205, 149, 32, 150, 155, 31, 83, 16, 173, 159, 46, 146, 244, 46, 8, 98, 254, 4, 246, 42, 120, 156, 78, 35, 223, 143, 83, 112, 239, 122, 2, 17, 0, 0, 0, 4, 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