Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7894fae6d15a99e1309aa4b0bdbeb85d2bf4a1c6b51af0a8bf766a81605cbb75

Tx prefix hash: b81549282d42a6b387f74d12335ae89854387650843e82d43c36e2db8a2306f2
Tx public key: 5e1c271f9075f41d0552dfc26862fe5a908a15e2d594ec33743e34b0759e2406
Timestamp: 1720583677 Timestamp [UCT]: 2024-07-10 03:54:37 Age [y:d:h:m:s]: 01:129:10:02:06
Block: 1062400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351006 RingCT/type: yes/0
Extra: 015e1c271f9075f41d0552dfc26862fe5a908a15e2d594ec33743e34b0759e2406021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14c086bdb6cefca85a6897481c0f9e49ac2240aa85de9dbe5bf21476f304d488 0.600000000000 1532901 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": 1062410, "vin": [ { "gen": { "height": 1062400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14c086bdb6cefca85a6897481c0f9e49ac2240aa85de9dbe5bf21476f304d488" } } ], "extra": [ 1, 94, 28, 39, 31, 144, 117, 244, 29, 5, 82, 223, 194, 104, 98, 254, 90, 144, 138, 21, 226, 213, 148, 236, 51, 116, 62, 52, 176, 117, 158, 36, 6, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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