Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3ad6b57be2ef3d4eeefa385e061456f70a57fdc7ab88bb7514fc75bb123cc8

Tx prefix hash: a2676b78f5b0ef8411bd26033c6e0e65ab9883d8686021725378d52e8ad90df0
Tx public key: 8aa2fda112a4e76daca0bb6144ca99f4815c39df9c02c29753e3443a2bc2444d
Timestamp: 1718281269 Timestamp [UCT]: 2024-06-13 12:21:09 Age [y:d:h:m:s]: 00:277:14:06:54
Block: 1043308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198368 RingCT/type: yes/0
Extra: 018aa2fda112a4e76daca0bb6144ca99f4815c39df9c02c29753e3443a2bc2444d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48a7e36efa2ff0599372b35b4a3c2bb3a74358fc92b231c88f1a98a47e7517fb 0.600000000000 1512429 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": 1043318, "vin": [ { "gen": { "height": 1043308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48a7e36efa2ff0599372b35b4a3c2bb3a74358fc92b231c88f1a98a47e7517fb" } } ], "extra": [ 1, 138, 162, 253, 161, 18, 164, 231, 109, 172, 160, 187, 97, 68, 202, 153, 244, 129, 92, 57, 223, 156, 2, 194, 151, 83, 227, 68, 58, 43, 194, 68, 77, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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