Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d949eabe8eac6bce0a508c6377a9e12a97420e25bcd483b62ec7a4f382e006dd

Tx prefix hash: 4361984b4c7d2c6754da126daa58e562bf0c3e1a2dd0382507d9fdbc6bd1986e
Tx public key: 4680242584c5dddf2d0ea3305dc59d632834114ed924c5ff61c8fa6310990de1
Timestamp: 1722707937 Timestamp [UCT]: 2024-08-03 17:58:57 Age [y:d:h:m:s]: 00:318:03:47:10
Block: 1079997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227212 RingCT/type: yes/0
Extra: 014680242584c5dddf2d0ea3305dc59d632834114ed924c5ff61c8fa6310990de102110000000be914dd15000000000000000000

1 output(s) for total of 0.615570000000 dcy

stealth address amount amount idx
00: 91937b236f645132c6a587c6fb2e8d73c2d8d9a0f7e8f649ad6f40adec83e1df 0.615570000000 1553186 of 0

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": 1080007, "vin": [ { "gen": { "height": 1079997 } } ], "vout": [ { "amount": 615570000, "target": { "key": "91937b236f645132c6a587c6fb2e8d73c2d8d9a0f7e8f649ad6f40adec83e1df" } } ], "extra": [ 1, 70, 128, 36, 37, 132, 197, 221, 223, 45, 14, 163, 48, 93, 197, 157, 99, 40, 52, 17, 78, 217, 36, 197, 255, 97, 200, 250, 99, 16, 153, 13, 225, 2, 17, 0, 0, 0, 11, 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