Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339f5d5f2332407251533dcebb26c86455f2c93b10f5edaa82c5cc132b208179

Tx prefix hash: 8a4cbdb36817ae13b619c28409753725bb9b9b5667df74124d6d4f2a972a88fa
Tx public key: b3e71e95a0f88897f69725f45ac6407a2da4ffc1400a49702acf7d864a3e37d5
Timestamp: 1717819347 Timestamp [UCT]: 2024-06-08 04:02:27 Age [y:d:h:m:s]: 01:159:04:49:59
Block: 1039481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372359 RingCT/type: yes/0
Extra: 01b3e71e95a0f88897f69725f45ac6407a2da4ffc1400a49702acf7d864a3e37d5021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ceb4a61fbbf445e1052e2e3d815f483f51d46a5bec48425034d5fbe6a0e9258 0.600000000000 1508124 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": 1039491, "vin": [ { "gen": { "height": 1039481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ceb4a61fbbf445e1052e2e3d815f483f51d46a5bec48425034d5fbe6a0e9258" } } ], "extra": [ 1, 179, 231, 30, 149, 160, 248, 136, 151, 246, 151, 37, 244, 90, 198, 64, 122, 45, 164, 255, 193, 64, 10, 73, 112, 42, 207, 125, 134, 74, 62, 55, 213, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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