Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2302f79f9d08e6139aaa85142e90920b03cc26697d27f40313a1a962a5418021

Tx prefix hash: 34cd0d4cedafd58b7a6be70e3b2de5ae2d96b0313d9c70ea9adf9e076ba7df3d
Tx public key: dca8e3180865c6270a6a38af915e9afeab2e5280fcd99f7d24d441d69377cc32
Timestamp: 1702389447 Timestamp [UCT]: 2023-12-12 13:57:27 Age [y:d:h:m:s]: 01:331:22:42:25
Block: 911573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496071 RingCT/type: yes/0
Extra: 01dca8e3180865c6270a6a38af915e9afeab2e5280fcd99f7d24d441d69377cc3202110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b856acc1c0979e594c7fd6bba702fd5ac498b670fddfb0163a1104239ae5416a 0.600000000000 1368785 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": 911583, "vin": [ { "gen": { "height": 911573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b856acc1c0979e594c7fd6bba702fd5ac498b670fddfb0163a1104239ae5416a" } } ], "extra": [ 1, 220, 168, 227, 24, 8, 101, 198, 39, 10, 106, 56, 175, 145, 94, 154, 254, 171, 46, 82, 128, 252, 217, 159, 125, 36, 212, 65, 214, 147, 119, 204, 50, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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