Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a914d4f3cdd72e0a6a5704d4c2adca7cb72990fd0de0422abcacb88a2ff18c0

Tx prefix hash: fbea27a8a66f3c0131b14f18018f3dce08e3f6258ff0a7c9646d2050781543a4
Tx public key: 3e40c473ef18f9a8d9d766b160e4521474979a47f266d9f16cb750ef07980adf
Timestamp: 1729335308 Timestamp [UCT]: 2024-10-19 10:55:08 Age [y:d:h:m:s]: 00:196:02:54:08
Block: 1134943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139965 RingCT/type: yes/0
Extra: 013e40c473ef18f9a8d9d766b160e4521474979a47f266d9f16cb750ef07980adf0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10347af300fc4b37781b59121fc722629ce58f7c7b80596bb4bf0ce46aac19a0 0.600000000000 1618270 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": 1134953, "vin": [ { "gen": { "height": 1134943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10347af300fc4b37781b59121fc722629ce58f7c7b80596bb4bf0ce46aac19a0" } } ], "extra": [ 1, 62, 64, 196, 115, 239, 24, 249, 168, 217, 215, 102, 177, 96, 228, 82, 20, 116, 151, 154, 71, 242, 102, 217, 241, 108, 183, 80, 239, 7, 152, 10, 223, 2, 17, 0, 0, 0, 1, 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