Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87816de6812ad52e8ec5fcb74b214fc44d8ed80f05a64bb1d633265451933f4f

Tx prefix hash: a34ee2996073c6600ba8071fb069e6df7e3bcfe972475a5606a2699d51487791
Tx public key: 9ff8893d0cd16e622076ce471e7a208f5a30af45318a2b1b883af8cd41e9e0a4
Timestamp: 1727992920 Timestamp [UCT]: 2024-10-03 22:02:00 Age [y:d:h:m:s]: 00:163:10:47:38
Block: 1123821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116624 RingCT/type: yes/0
Extra: 019ff8893d0cd16e622076ce471e7a208f5a30af45318a2b1b883af8cd41e9e0a402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7672ca7d059e98bbab98d85f65d5f74bd0babf4359ea705811471d373d35e6 0.600000000000 1606356 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": 1123831, "vin": [ { "gen": { "height": 1123821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7672ca7d059e98bbab98d85f65d5f74bd0babf4359ea705811471d373d35e6" } } ], "extra": [ 1, 159, 248, 137, 61, 12, 209, 110, 98, 32, 118, 206, 71, 30, 122, 32, 143, 90, 48, 175, 69, 49, 138, 43, 27, 136, 58, 248, 205, 65, 233, 224, 164, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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