Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7657aef5bcf166621d5fc3816863529585e4f3d93e34bd39d3c7e59f5e91e07

Tx prefix hash: 1844a3de529332ebe43f13e6a9c5efc45a146a161c872c1d2b1bee43fb7c0e65
Tx public key: dbd87bbf951aa0b4d0e860627dcb6c4eb7e92e135fd7f3409bdb42422034c9cb
Timestamp: 1738310383 Timestamp [UCT]: 2025-01-31 07:59:43 Age [y:d:h:m:s]: 00:339:14:07:05
Block: 1208932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240549 RingCT/type: yes/0
Extra: 01dbd87bbf951aa0b4d0e860627dcb6c4eb7e92e135fd7f3409bdb42422034c9cb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b714db8c8755468833af7f942ee5cd9bb9249a33657961b4cffcdc2e070bca3d 0.600000000000 1695669 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": 1208942, "vin": [ { "gen": { "height": 1208932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b714db8c8755468833af7f942ee5cd9bb9249a33657961b4cffcdc2e070bca3d" } } ], "extra": [ 1, 219, 216, 123, 191, 149, 26, 160, 180, 208, 232, 96, 98, 125, 203, 108, 78, 183, 233, 46, 19, 95, 215, 243, 64, 155, 219, 66, 66, 32, 52, 201, 203, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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