Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6f198251c6b6298a56dd5250e17b5b43d0dbd1cb99310990c7efe55d60633d0

Tx prefix hash: 2306bdbe21019c0719627e4f421fa0fb118f600a3f2080b628baffe6e5039d75
Tx public key: 865bbcd39aa3aa272cad85a4586aee2ce07f9d272c30106dbf95c22e5bde6e43
Timestamp: 1717640434 Timestamp [UCT]: 2024-06-06 02:20:34 Age [y:d:h:m:s]: 01:156:16:35:50
Block: 1037982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370573 RingCT/type: yes/0
Extra: 01865bbcd39aa3aa272cad85a4586aee2ce07f9d272c30106dbf95c22e5bde6e4302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c805f893edaac9562247033874d089e8b82ae5b9e0d878e2fd2a19bc3a6b13 0.600000000000 1506541 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": 1037992, "vin": [ { "gen": { "height": 1037982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c805f893edaac9562247033874d089e8b82ae5b9e0d878e2fd2a19bc3a6b13" } } ], "extra": [ 1, 134, 91, 188, 211, 154, 163, 170, 39, 44, 173, 133, 164, 88, 106, 238, 44, 224, 127, 157, 39, 44, 48, 16, 109, 191, 149, 194, 46, 91, 222, 110, 67, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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