Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ae7ee5fb2980e62ecfaaccc2ca0578850aea34468ec963d1ae0105c12eece0

Tx prefix hash: ee9ef1eb74eae5bd1874c10b4cae0fe0d5ae827745a971d95c71d174689d7000
Tx public key: 0e3eb9a18255b6ce18fea654369d754d3188ba0c325ecb838fd5f50d218b09e8
Timestamp: 1738675083 Timestamp [UCT]: 2025-02-04 13:18:03 Age [y:d:h:m:s]: 00:357:10:52:18
Block: 1211950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253143 RingCT/type: yes/0
Extra: 010e3eb9a18255b6ce18fea654369d754d3188ba0c325ecb838fd5f50d218b09e8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11b88adb1e1f47ad39059f9610e11f227a0ec05e69f452e47fa28876cc0dc33c 0.600000000000 1698717 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": 1211960, "vin": [ { "gen": { "height": 1211950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b88adb1e1f47ad39059f9610e11f227a0ec05e69f452e47fa28876cc0dc33c" } } ], "extra": [ 1, 14, 62, 185, 161, 130, 85, 182, 206, 24, 254, 166, 84, 54, 157, 117, 77, 49, 136, 186, 12, 50, 94, 203, 131, 143, 213, 245, 13, 33, 139, 9, 232, 2, 17, 0, 0, 0, 6, 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