Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e28b952e15f7e42e7fbf405093764d240f8cf83237ab524310a91f8881106195

Tx prefix hash: 0f4dc7a37e3d4e8b700684f70660c37749366ad3ba7125f801c5e9ed8668813d
Tx public key: a08daba6ef08c720bd9a3bd7b9a902c23f5418fcbdd9dcc4a0b851415df616fb
Timestamp: 1726329626 Timestamp [UCT]: 2024-09-14 16:00:26 Age [y:d:h:m:s]: 00:182:17:41:15
Block: 1110024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130446 RingCT/type: yes/0
Extra: 01a08daba6ef08c720bd9a3bd7b9a902c23f5418fcbdd9dcc4a0b851415df616fb021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 682846dfaac6a0f88f6f05871b13a1223ef38ed436a0a1be5370fc2d30b453f3 0.600000000000 1588485 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": 1110034, "vin": [ { "gen": { "height": 1110024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "682846dfaac6a0f88f6f05871b13a1223ef38ed436a0a1be5370fc2d30b453f3" } } ], "extra": [ 1, 160, 141, 171, 166, 239, 8, 199, 32, 189, 154, 59, 215, 185, 169, 2, 194, 63, 84, 24, 252, 189, 217, 220, 196, 160, 184, 81, 65, 93, 246, 22, 251, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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