Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea1ff2226cf90372b06a9196b6c373bf678328f8f77f10927e79c42c6b2d7ac7

Tx prefix hash: d48d2501e9a2c95d3c1867b7c759fb4357154040142a422143f8b900915de475
Tx public key: 81f5bc5e19b5376b6f1c64399508f71eda0dd22b652467aef3a89959bc64d014
Timestamp: 1722166205 Timestamp [UCT]: 2024-07-28 11:30:05 Age [y:d:h:m:s]: 01:101:05:03:39
Block: 1075504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330818 RingCT/type: yes/0
Extra: 0181f5bc5e19b5376b6f1c64399508f71eda0dd22b652467aef3a89959bc64d01402110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652a6fcaa5faca34dab6b9657278c5e1f2a0db7072c8b4c33fef270bad4c257f 0.600000000000 1548033 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": 1075514, "vin": [ { "gen": { "height": 1075504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652a6fcaa5faca34dab6b9657278c5e1f2a0db7072c8b4c33fef270bad4c257f" } } ], "extra": [ 1, 129, 245, 188, 94, 25, 181, 55, 107, 111, 28, 100, 57, 149, 8, 247, 30, 218, 13, 210, 43, 101, 36, 103, 174, 243, 168, 153, 89, 188, 100, 208, 20, 2, 17, 0, 0, 0, 9, 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