Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d764beabb4849c509b5f68d1f2b30053cbf3b765ab18c17992dbdc528f469f5

Tx prefix hash: b9642b66abf98ad4bed36b683ac352da29efb7a2e9c753c3a6577b6443817c8d
Tx public key: 0f9fbd52f2731b37e1c8d915082c7ad6169d0c96733aa22d1021aeca1b4b6035
Timestamp: 1713084685 Timestamp [UCT]: 2024-04-14 08:51:25 Age [y:d:h:m:s]: 00:215:01:54:09
Block: 1000208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153987 RingCT/type: yes/0
Extra: 010f9fbd52f2731b37e1c8d915082c7ad6169d0c96733aa22d1021aeca1b4b60350211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198403b1ca3ef4b1ded99851902acbe99c99e4f2ba6baa3b8a248e15fa8a740d 0.600000000000 1460704 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": 1000218, "vin": [ { "gen": { "height": 1000208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198403b1ca3ef4b1ded99851902acbe99c99e4f2ba6baa3b8a248e15fa8a740d" } } ], "extra": [ 1, 15, 159, 189, 82, 242, 115, 27, 55, 225, 200, 217, 21, 8, 44, 122, 214, 22, 157, 12, 150, 115, 58, 162, 45, 16, 33, 174, 202, 27, 75, 96, 53, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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