Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a45514326da2d870411cc68d50956b836fb9fb1be476375f2c83f2a838fb87

Tx prefix hash: 6f08aa4feb754e614f16e4f14d825ec670189920d51c7542bdc03d6031ccf1d8
Tx public key: 493180fdd9330b96a4213aef250183d5d63470d19101afdd269c4abdac027bed
Timestamp: 1699084314 Timestamp [UCT]: 2023-11-04 07:51:54 Age [y:d:h:m:s]: 01:192:10:15:04
Block: 884360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398557 RingCT/type: yes/0
Extra: 01493180fdd9330b96a4213aef250183d5d63470d19101afdd269c4abdac027bed02110000000133af99f4000000000000000000

1 output(s) for total of 0.720689527000 dcy

stealth address amount amount idx
00: dcdffc44d44ff6f531c44f3df964f6fdb69a70278f8420768e45df7a55324469 0.720689527000 1340097 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": 884370, "vin": [ { "gen": { "height": 884360 } } ], "vout": [ { "amount": 720689527, "target": { "key": "dcdffc44d44ff6f531c44f3df964f6fdb69a70278f8420768e45df7a55324469" } } ], "extra": [ 1, 73, 49, 128, 253, 217, 51, 11, 150, 164, 33, 58, 239, 37, 1, 131, 213, 214, 52, 112, 209, 145, 1, 175, 221, 38, 156, 74, 189, 172, 2, 123, 237, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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