Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f8040d14be23ba637e866e7427d3037d0b6e3a7f65be3cff0d26c72c670d54

Tx prefix hash: fc80ad6fa5379c174d280d7bccf4f5598ae2cb5db1bba4ad07c0713211d30953
Tx public key: 5b584c87854afcef0eb7a80121e1c5a9cd553b3ad64f1e2df611780b1833b016
Timestamp: 1731719624 Timestamp [UCT]: 2024-11-16 01:13:44 Age [y:d:h:m:s]: 00:148:02:37:10
Block: 1154636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105662 RingCT/type: yes/0
Extra: 015b584c87854afcef0eb7a80121e1c5a9cd553b3ad64f1e2df611780b1833b016021100000011007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 430bb3579efd5f0d7f277aae291932926f49baa48b98eb32cda0bb8057fa6fc8 0.600000000000 1640249 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": 1154646, "vin": [ { "gen": { "height": 1154636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "430bb3579efd5f0d7f277aae291932926f49baa48b98eb32cda0bb8057fa6fc8" } } ], "extra": [ 1, 91, 88, 76, 135, 133, 74, 252, 239, 14, 183, 168, 1, 33, 225, 197, 169, 205, 85, 59, 58, 214, 79, 30, 45, 246, 17, 120, 11, 24, 51, 176, 22, 2, 17, 0, 0, 0, 17, 0, 127, 151, 138, 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