Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf3a7cbce71d41b576486210df4de58ebf75dd3e7bf53ea42ad9274610deeb92

Tx prefix hash: f1f9ca40ff22ee72fea505d2afb02fba47c1868e3181b98ccb8dde981b0ddafd
Tx public key: 9d935469ae467a1ab551b3f0e2a15cdcbd548474676ae37163da6d9ee4a3993e
Timestamp: 1698235611 Timestamp [UCT]: 2023-10-25 12:06:51 Age [y:d:h:m:s]: 01:090:18:42:18
Block: 877337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326064 RingCT/type: yes/0
Extra: 019d935469ae467a1ab551b3f0e2a15cdcbd548474676ae37163da6d9ee4a3993e021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.760358378000 dcy

stealth address amount amount idx
00: 00bcc0106f7c28d4f8942b2b65666c1da13d4fb5cdaa08e8f2b2d7a9c62bdb3d 0.760358378000 1332711 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": 877347, "vin": [ { "gen": { "height": 877337 } } ], "vout": [ { "amount": 760358378, "target": { "key": "00bcc0106f7c28d4f8942b2b65666c1da13d4fb5cdaa08e8f2b2d7a9c62bdb3d" } } ], "extra": [ 1, 157, 147, 84, 105, 174, 70, 122, 26, 181, 81, 179, 240, 226, 161, 92, 220, 189, 84, 132, 116, 103, 106, 227, 113, 99, 218, 109, 158, 228, 163, 153, 62, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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