Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11ab087567bd754dabd117394fa5da84332b7e4ea2f47636b1c75095841f041

Tx prefix hash: cc8bf75be3d58399eea09d2d04a3a0ca61596c51c27376a37740baf3800fb603
Tx public key: c48539e4f7cb1aa5f41b040a38494bce8b25d24d83921175c3a43dabb798e07e
Timestamp: 1732969010 Timestamp [UCT]: 2024-11-30 12:16:50 Age [y:d:h:m:s]: 00:123:15:19:06
Block: 1164980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88152 RingCT/type: yes/0
Extra: 01c48539e4f7cb1aa5f41b040a38494bce8b25d24d83921175c3a43dabb798e07e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c435b88d9f029435809ff1bb93e2f76194a7464772ef1748a6351a3fed633852 0.600000000000 1650655 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": 1164990, "vin": [ { "gen": { "height": 1164980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c435b88d9f029435809ff1bb93e2f76194a7464772ef1748a6351a3fed633852" } } ], "extra": [ 1, 196, 133, 57, 228, 247, 203, 26, 165, 244, 27, 4, 10, 56, 73, 75, 206, 139, 37, 210, 77, 131, 146, 17, 117, 195, 164, 61, 171, 183, 152, 224, 126, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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