Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff24b044067f99edf95b533100c18c709ab154ecb947b4ac8eb59d5c2b4cd8a8

Tx prefix hash: 61685b2ea1019c67ebe8ab3d782271276bd163187a1baa3d0c0195272b537dc0
Tx public key: d5586fea2a5437486c59d7fdb36b11e4689eff9d1454b6e12c66ab6e0c64dff3
Timestamp: 1707641618 Timestamp [UCT]: 2024-02-11 08:53:38 Age [y:d:h:m:s]: 01:133:00:08:22
Block: 955086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355944 RingCT/type: yes/0
Extra: 01d5586fea2a5437486c59d7fdb36b11e4689eff9d1454b6e12c66ab6e0c64dff302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8acc6f8c2c0afc4428346588aa1033c5fc27cf6471a0545087ad121cb16ff8a 0.600000000000 1414368 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": 955096, "vin": [ { "gen": { "height": 955086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8acc6f8c2c0afc4428346588aa1033c5fc27cf6471a0545087ad121cb16ff8a" } } ], "extra": [ 1, 213, 88, 111, 234, 42, 84, 55, 72, 108, 89, 215, 253, 179, 107, 17, 228, 104, 158, 255, 157, 20, 84, 182, 225, 44, 102, 171, 110, 12, 100, 223, 243, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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