Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3b9af7f4852b145025e17a3960e4cc749cd47fbe586f068b7e9d899c3678935

Tx prefix hash: 89128f2dc183764c3598d9e3295e2fac160434419f0c5b464539669e4e9f69e9
Tx public key: c91a44f1430068420dc9738b487763561ccdf83cf928c0bd5d87f0ca6e0d6235
Timestamp: 1710310081 Timestamp [UCT]: 2024-03-13 06:08:01 Age [y:d:h:m:s]: 01:241:09:58:02
Block: 977236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431237 RingCT/type: yes/0
Extra: 01c91a44f1430068420dc9738b487763561ccdf83cf928c0bd5d87f0ca6e0d62350211000000137a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c39c8cc35ef2d4637cbfb6f349b9619d205ecd08857ed2cb95a10d200b00c2 0.600000000000 1437237 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": 977246, "vin": [ { "gen": { "height": 977236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c39c8cc35ef2d4637cbfb6f349b9619d205ecd08857ed2cb95a10d200b00c2" } } ], "extra": [ 1, 201, 26, 68, 241, 67, 0, 104, 66, 13, 201, 115, 139, 72, 119, 99, 86, 28, 205, 248, 60, 249, 40, 192, 189, 93, 135, 240, 202, 110, 13, 98, 53, 2, 17, 0, 0, 0, 19, 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