Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8dd4dc0d56ff12b9160056ff3a9df4be625fd8d7b5c653f57959e127eec758f

Tx prefix hash: 5f2ef31292a58012edd11188043931641858b58b77b7e19ae749f65d429ae72d
Tx public key: 80181fa1ac79381d36ad9076d7116cb5071103a5d4a0222903ff38b333dc4f2d
Timestamp: 1718164955 Timestamp [UCT]: 2024-06-12 04:02:35 Age [y:d:h:m:s]: 00:278:08:46:55
Block: 1042348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198935 RingCT/type: yes/0
Extra: 0180181fa1ac79381d36ad9076d7116cb5071103a5d4a0222903ff38b333dc4f2d021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cc62b56ab6e8a4200470a81d4a952f0d4ecfd1a3382c93b901537c78fa2f3df 0.600000000000 1511245 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": 1042358, "vin": [ { "gen": { "height": 1042348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cc62b56ab6e8a4200470a81d4a952f0d4ecfd1a3382c93b901537c78fa2f3df" } } ], "extra": [ 1, 128, 24, 31, 161, 172, 121, 56, 29, 54, 173, 144, 118, 215, 17, 108, 181, 7, 17, 3, 165, 212, 160, 34, 41, 3, 255, 56, 179, 51, 220, 79, 45, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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