Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14113944baa8f5b34c46af4b4f0eef46d1a47597833f29f9d8ff0f9bf2b21cf

Tx prefix hash: 275eb8931b61af1a72efad18bd8ad000280c37c8f2475cf5e278ec8968326184
Tx public key: 996e6042bfc6cb76dca81a1bc1cf2981173bb7275d2e435af12e0e05e40c9774
Timestamp: 1694575623 Timestamp [UCT]: 2023-09-13 03:27:03 Age [y:d:h:m:s]: 01:183:12:08:13
Block: 846958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392255 RingCT/type: yes/0
Extra: 01996e6042bfc6cb76dca81a1bc1cf2981173bb7275d2e435af12e0e05e40c9774021100000003faf35c9c000000000000000000

1 output(s) for total of 0.958686514000 dcy

stealth address amount amount idx
00: e926fe0cbdb93c2ff34f8739cdbabd2faea63e52f0740518be59aec1e010f3f5 0.958686514000 1300452 of 0

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": 846968, "vin": [ { "gen": { "height": 846958 } } ], "vout": [ { "amount": 958686514, "target": { "key": "e926fe0cbdb93c2ff34f8739cdbabd2faea63e52f0740518be59aec1e010f3f5" } } ], "extra": [ 1, 153, 110, 96, 66, 191, 198, 203, 118, 220, 168, 26, 27, 193, 207, 41, 129, 23, 59, 183, 39, 93, 46, 67, 90, 241, 46, 14, 5, 228, 12, 151, 116, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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