Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3629bb9a73d7c398509f47f1da44344a56e781ab6864ccfc7719d2108d79e98c

Tx prefix hash: 41a85f6168b44f9870c04e072b8eb9ee2fe34b5d9edb662f7aa7ea77a74bfe7d
Tx public key: 4f86a08569897a60c1666e539ac2c1a93eb07ec9de6fc9dc584380055978bc91
Timestamp: 1714745042 Timestamp [UCT]: 2024-05-03 14:04:02 Age [y:d:h:m:s]: 01:049:14:41:03
Block: 1013995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296225 RingCT/type: yes/0
Extra: 014f86a08569897a60c1666e539ac2c1a93eb07ec9de6fc9dc584380055978bc910211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ca8f392faa43d574c330e5898e52de4e54f59d98c70d42cc3762a7d3b197fb4 0.600000000000 1476962 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": 1014005, "vin": [ { "gen": { "height": 1013995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ca8f392faa43d574c330e5898e52de4e54f59d98c70d42cc3762a7d3b197fb4" } } ], "extra": [ 1, 79, 134, 160, 133, 105, 137, 122, 96, 193, 102, 110, 83, 154, 194, 193, 169, 62, 176, 126, 201, 222, 111, 201, 220, 88, 67, 128, 5, 89, 120, 188, 145, 2, 17, 0, 0, 0, 7, 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