Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b06287c88ee4783e53f75feb8986005d5d8874c1ad6bb5a0f11421872d1320d

Tx prefix hash: 3a274d450a70341e91824f6281648ae776dacf369acef002cea57cd1027b866a
Tx public key: 3b2ffac131f7567da8e1f41ee7455fe50506cd6df40b7bb04540cb4ea5db56f0
Timestamp: 1699802328 Timestamp [UCT]: 2023-11-12 15:18:48 Age [y:d:h:m:s]: 01:065:21:38:03
Block: 890111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308494 RingCT/type: yes/0
Extra: 013b2ffac131f7567da8e1f41ee7455fe50506cd6df40b7bb04540cb4ea5db56f0021100000001faf35c9c000000000000000000

1 output(s) for total of 0.689751657000 dcy

stealth address amount amount idx
00: 4dccccc31e363307e5f77646bb30d633c35271d85acee3a862bfe58e5e592266 0.689751657000 1346130 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": 890121, "vin": [ { "gen": { "height": 890111 } } ], "vout": [ { "amount": 689751657, "target": { "key": "4dccccc31e363307e5f77646bb30d633c35271d85acee3a862bfe58e5e592266" } } ], "extra": [ 1, 59, 47, 250, 193, 49, 247, 86, 125, 168, 225, 244, 30, 231, 69, 95, 229, 5, 6, 205, 109, 244, 11, 123, 176, 69, 64, 203, 78, 165, 219, 86, 240, 2, 17, 0, 0, 0, 1, 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