Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486f0b0aed5fbb8a46de760ffc2837a4164c009735b55070bd6b85fb4cbfac34

Tx prefix hash: 0a330e828482d3194c5e75e6d45f91ed9680a7152d5ebeb966e833968ab1f07b
Tx public key: 081294d12fb4a618ef5d82c53c9f5fff599f93f7afba57604c9d7020f495a5c2
Timestamp: 1704342987 Timestamp [UCT]: 2024-01-04 04:36:27 Age [y:d:h:m:s]: 01:096:17:44:02
Block: 927754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330234 RingCT/type: yes/0
Extra: 01081294d12fb4a618ef5d82c53c9f5fff599f93f7afba57604c9d7020f495a5c2021100000007679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8637680265dc860bd1cca51d900becc1ea2bd360570b91a31973ae62545f40ec 0.600000000000 1385590 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": 927764, "vin": [ { "gen": { "height": 927754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8637680265dc860bd1cca51d900becc1ea2bd360570b91a31973ae62545f40ec" } } ], "extra": [ 1, 8, 18, 148, 209, 47, 180, 166, 24, 239, 93, 130, 197, 60, 159, 95, 255, 89, 159, 147, 247, 175, 186, 87, 96, 76, 157, 112, 32, 244, 149, 165, 194, 2, 17, 0, 0, 0, 7, 103, 154, 138, 129, 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