Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba7a033dc61ed84c1285e66f8882931bfbc3c70761f55484341909b29f644d03

Tx prefix hash: c78c5ccc0a0b9b3abf8ce8c74bd21c61109f60455822924c6f305dee8ae01ac1
Tx public key: c1551da43fcea6fdf3d438e9ae049303445a2cb04e737ea8ebb38de2fa35612a
Timestamp: 1730803002 Timestamp [UCT]: 2024-11-05 10:36:42 Age [y:d:h:m:s]: 00:229:00:56:46
Block: 1147031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163382 RingCT/type: yes/0
Extra: 01c1551da43fcea6fdf3d438e9ae049303445a2cb04e737ea8ebb38de2fa35612a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c11f68b5ee5a8291d96cfa552a9aed74615f8aa3028ab2393043dcc580d1602 0.600000000000 1631724 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": 1147041, "vin": [ { "gen": { "height": 1147031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c11f68b5ee5a8291d96cfa552a9aed74615f8aa3028ab2393043dcc580d1602" } } ], "extra": [ 1, 193, 85, 29, 164, 63, 206, 166, 253, 243, 212, 56, 233, 174, 4, 147, 3, 68, 90, 44, 176, 78, 115, 126, 168, 235, 179, 141, 226, 250, 53, 97, 42, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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