Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415dc923ac7516fbbd8759a318578bff5e3ef5f73efc8a17bfd25b2ed3f6e9f3

Tx prefix hash: 04534a7a314aad0b93c4c88e4c29a6637775a57e5027da2a77db9e3aa8896459
Tx public key: be84a90e0db769f795801112c4d688c160d364913cb4723ce8cfdebd206b7a62
Timestamp: 1736462945 Timestamp [UCT]: 2025-01-09 22:49:05 Age [y:d:h:m:s]: 00:086:06:57:53
Block: 1193909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61446 RingCT/type: yes/0
Extra: 01be84a90e0db769f795801112c4d688c160d364913cb4723ce8cfdebd206b7a620211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53c9d9a52966547442cc1f8caa31caa0cf8a23b3c6da9d26ce1a58948e8e9c54 0.600000000000 1680474 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": 1193919, "vin": [ { "gen": { "height": 1193909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53c9d9a52966547442cc1f8caa31caa0cf8a23b3c6da9d26ce1a58948e8e9c54" } } ], "extra": [ 1, 190, 132, 169, 14, 13, 183, 105, 247, 149, 128, 17, 18, 196, 214, 136, 193, 96, 211, 100, 145, 60, 180, 114, 60, 232, 207, 222, 189, 32, 107, 122, 98, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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