Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815ecb35c5fc0e527e2ee1d382a0ac0c3da202611159f14163d1dbf75793473d

Tx prefix hash: 873c5ef8eb9e67e522f0572ab7543626f9dfa05683498ff2aec5d34ad9b53a6e
Tx public key: 3818e6d400fc4354d031d68429e62fd1681729a93f655b05e36a8969597628aa
Timestamp: 1705652949 Timestamp [UCT]: 2024-01-19 08:29:09 Age [y:d:h:m:s]: 01:075:11:40:50
Block: 938591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315036 RingCT/type: yes/0
Extra: 013818e6d400fc4354d031d68429e62fd1681729a93f655b05e36a8969597628aa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02207768fd2f5790c6cbed9d15a29703a8b0b6ebb2ab1749d028f00cd07fdf6 0.600000000000 1396661 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": 938601, "vin": [ { "gen": { "height": 938591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02207768fd2f5790c6cbed9d15a29703a8b0b6ebb2ab1749d028f00cd07fdf6" } } ], "extra": [ 1, 56, 24, 230, 212, 0, 252, 67, 84, 208, 49, 214, 132, 41, 230, 47, 209, 104, 23, 41, 169, 63, 101, 91, 5, 227, 106, 137, 105, 89, 118, 40, 170, 2, 17, 0, 0, 0, 1, 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