Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40db4fccc9036db1fae8f7a1e48eb025cdef09d77d4a39795082b46c95c6d6e

Tx prefix hash: 7ee35a1cbe1062bc0317198ce4de5ad8da0e6fa671cdeab58ad11ebf42d6e3dd
Tx public key: ea224dc9e9c39bc03d7823084d61f416ea60415c7a8b6e54a34ba75c5072481f
Timestamp: 1705047411 Timestamp [UCT]: 2024-01-12 08:16:51 Age [y:d:h:m:s]: 01:108:08:51:28
Block: 933574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338577 RingCT/type: yes/0
Extra: 01ea224dc9e9c39bc03d7823084d61f416ea60415c7a8b6e54a34ba75c5072481f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 232ed5816098e9f503a3533eb659778731b59744a7a26f01ec75c573ecee7d02 0.600000000000 1391540 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": 933584, "vin": [ { "gen": { "height": 933574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "232ed5816098e9f503a3533eb659778731b59744a7a26f01ec75c573ecee7d02" } } ], "extra": [ 1, 234, 34, 77, 201, 233, 195, 155, 192, 61, 120, 35, 8, 77, 97, 244, 22, 234, 96, 65, 92, 122, 139, 110, 84, 163, 75, 167, 92, 80, 114, 72, 31, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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