Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb446fb00956fcc9d87e7f874848d7819d6f44c7b425c92d0d1dac4e4c2f3809

Tx prefix hash: 84ef4ef2e0c0c181171adbec0902cf13de6471ac17f731eeff1e1800f95c1a9a
Tx public key: 5654116c92c97fd3cf8099a07c98cc86ccd5f989d53ab4b7cc9d866b7354774a
Timestamp: 1737743619 Timestamp [UCT]: 2025-01-24 18:33:39 Age [y:d:h:m:s]: 00:331:07:52:18
Block: 1204458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234392 RingCT/type: yes/0
Extra: 015654116c92c97fd3cf8099a07c98cc86ccd5f989d53ab4b7cc9d866b7354774a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acef0d4cab714b1cc96d81444445f98583ad9bc7c985eabf8fce4f253af66e2c 0.600000000000 1691145 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": 1204468, "vin": [ { "gen": { "height": 1204458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acef0d4cab714b1cc96d81444445f98583ad9bc7c985eabf8fce4f253af66e2c" } } ], "extra": [ 1, 86, 84, 17, 108, 146, 201, 127, 211, 207, 128, 153, 160, 124, 152, 204, 134, 204, 213, 249, 137, 213, 58, 180, 183, 204, 157, 134, 107, 115, 84, 119, 74, 2, 17, 0, 0, 0, 6, 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