Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7895d18ebe90d0f1cb601b78b7c2efd4fd91da5792308ecfb58345237517ed84

Tx prefix hash: d6220fc1920280e0a109ff29f541bf323b7a4bdf3daf02c180e1d2537ec47a4b
Tx public key: fb0e31388220e952fb2b2f1bd69fdb33e2ee8f11519bfa8c172687657a58d278
Timestamp: 1713504247 Timestamp [UCT]: 2024-04-19 05:24:07 Age [y:d:h:m:s]: 01:040:23:46:13
Block: 1003699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290274 RingCT/type: yes/0
Extra: 01fb0e31388220e952fb2b2f1bd69fdb33e2ee8f11519bfa8c172687657a58d278021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc89435dc1cd6bbb7da41a5f70ac31746c6a8e10e72779c125e824f4fac4ac1b 0.600000000000 1464241 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": 1003709, "vin": [ { "gen": { "height": 1003699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc89435dc1cd6bbb7da41a5f70ac31746c6a8e10e72779c125e824f4fac4ac1b" } } ], "extra": [ 1, 251, 14, 49, 56, 130, 32, 233, 82, 251, 43, 47, 27, 214, 159, 219, 51, 226, 238, 143, 17, 81, 155, 250, 140, 23, 38, 135, 101, 122, 88, 210, 120, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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