Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b11213b873c79c7954e4799ed79510b80c990405e33198f2de1a6dc4d8612f0

Tx prefix hash: 468d533c43bfa9db648bbb32607d8f51368c671798f2b1fb43d4a2621e2ea0bf
Tx public key: bd51ab501e94c0fc5a0f683e0ada1ee861c726822a2804eb85291ec3cfa810ca
Timestamp: 1732059202 Timestamp [UCT]: 2024-11-19 23:33:22 Age [y:d:h:m:s]: 00:004:06:52:53
Block: 1157443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3055 RingCT/type: yes/0
Extra: 01bd51ab501e94c0fc5a0f683e0ada1ee861c726822a2804eb85291ec3cfa810ca021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff325fbfe9e9ec013b1fa28168c1b11c79b02baf118eef472d896378af00e89e 0.600000000000 1643066 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": 1157453, "vin": [ { "gen": { "height": 1157443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff325fbfe9e9ec013b1fa28168c1b11c79b02baf118eef472d896378af00e89e" } } ], "extra": [ 1, 189, 81, 171, 80, 30, 148, 192, 252, 90, 15, 104, 62, 10, 218, 30, 232, 97, 199, 38, 130, 42, 40, 4, 235, 133, 41, 30, 195, 207, 168, 16, 202, 2, 17, 0, 0, 0, 1, 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