Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f55f039319428b3da386701dd97b7cd671a9f71163c621ed7ef89d6c4015a56

Tx prefix hash: 5235ce3e44e855974e5bbd3b1fce699de2c1990c4831f09590bb587d06faaacf
Tx public key: 32c54b07a2c416e1dd8d11393ad2b1c353dbe08ade4d2d397ef26d98f893fc3f
Timestamp: 1723944313 Timestamp [UCT]: 2024-08-18 01:25:13 Age [y:d:h:m:s]: 00:233:03:20:10
Block: 1090263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166475 RingCT/type: yes/0
Extra: 0132c54b07a2c416e1dd8d11393ad2b1c353dbe08ade4d2d397ef26d98f893fc3f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2945f7f48d6ef27edc5a0e1b4e66b65bfcff3bf618025233022a6ab2820a1bd 0.600000000000 1564886 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": 1090273, "vin": [ { "gen": { "height": 1090263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2945f7f48d6ef27edc5a0e1b4e66b65bfcff3bf618025233022a6ab2820a1bd" } } ], "extra": [ 1, 50, 197, 75, 7, 162, 196, 22, 225, 221, 141, 17, 57, 58, 210, 177, 195, 83, 219, 224, 138, 222, 77, 45, 57, 126, 242, 109, 152, 248, 147, 252, 63, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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