Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 491b5f8b62fe035eca9b1761934a9789e51a4dad7bfbdf8c5c98c8d606a24a9d

Tx prefix hash: 03dabe6c3bf18dfe82646df1074c4e9cc5087c56c08782e883df272348a8cd08
Tx public key: a98886cfccc4a864f9d4baf7527098faca0e1d04f2cb29db50e44aa7b7b7c31b
Timestamp: 1728155882 Timestamp [UCT]: 2024-10-05 19:18:02 Age [y:d:h:m:s]: 00:186:02:23:38
Block: 1125172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132800 RingCT/type: yes/0
Extra: 01a98886cfccc4a864f9d4baf7527098faca0e1d04f2cb29db50e44aa7b7b7c31b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4847ab4b089294a6db2e61c2d6f2717daa16f129a4860fb90f4a110875ae34d1 0.600000000000 1607849 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": 1125182, "vin": [ { "gen": { "height": 1125172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4847ab4b089294a6db2e61c2d6f2717daa16f129a4860fb90f4a110875ae34d1" } } ], "extra": [ 1, 169, 136, 134, 207, 204, 196, 168, 100, 249, 212, 186, 247, 82, 112, 152, 250, 202, 14, 29, 4, 242, 203, 41, 219, 80, 228, 74, 167, 183, 183, 195, 27, 2, 17, 0, 0, 0, 7, 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