Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20eeabfd6e01923d7fc083de4c0d1abf587951ea86dc4900000f634818b07746

Tx prefix hash: 2b38dec89b08934be09050d677f4a75fcfd68a7a4fbc58ce2334b609ae81867e
Tx public key: 5198184e971b59e4254d832ab12d012de8d51d74d04a2d7494a8bc3eb66aae7d
Timestamp: 1706650355 Timestamp [UCT]: 2024-01-30 21:32:35 Age [y:d:h:m:s]: 01:139:16:38:25
Block: 946862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360834 RingCT/type: yes/0
Extra: 015198184e971b59e4254d832ab12d012de8d51d74d04a2d7494a8bc3eb66aae7d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e6086487cef3c590735b39e67a403de813694636f674b6111a6475700fb3fd 0.600000000000 1405202 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": 946872, "vin": [ { "gen": { "height": 946862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e6086487cef3c590735b39e67a403de813694636f674b6111a6475700fb3fd" } } ], "extra": [ 1, 81, 152, 24, 78, 151, 27, 89, 228, 37, 77, 131, 42, 177, 45, 1, 45, 232, 213, 29, 116, 208, 74, 45, 116, 148, 168, 188, 62, 182, 106, 174, 125, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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