Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31bebcf1fc041a75234d6772917a36e63aaed89770e7e6fb6f88d0baa29b7fe8

Tx prefix hash: aaee9e20258217a2e8e59affda47d66e05b54b74f1f2b34b0e6eb2a024b81fe0
Tx public key: 982d21dbfa51d55ba11e7343aeb887d45c1dcbfeee8bdbfcae911d3904af1715
Timestamp: 1721758933 Timestamp [UCT]: 2024-07-23 18:22:13 Age [y:d:h:m:s]: 00:277:00:28:53
Block: 1072128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197935 RingCT/type: yes/0
Extra: 01982d21dbfa51d55ba11e7343aeb887d45c1dcbfeee8bdbfcae911d3904af171502110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db61d1511537b76e68bbc5701bc1361ee7a3a04a3df74f0ab33ac13a9a3f125a 0.600000000000 1544579 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": 1072138, "vin": [ { "gen": { "height": 1072128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db61d1511537b76e68bbc5701bc1361ee7a3a04a3df74f0ab33ac13a9a3f125a" } } ], "extra": [ 1, 152, 45, 33, 219, 250, 81, 213, 91, 161, 30, 115, 67, 174, 184, 135, 212, 92, 29, 203, 254, 238, 139, 219, 252, 174, 145, 29, 57, 4, 175, 23, 21, 2, 17, 0, 0, 0, 13, 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