Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dba83316d49907618fead0128b098029ffa1a14f547419c19950fa44765302c7

Tx prefix hash: 79ce352762014fc26848361358307e96dc1435f8ffc8ae94f4cdaf8b24012c03
Tx public key: 94c382b791f48169eeace53b0246635f79d6dfaf416f4907a2ae888e28b6311b
Timestamp: 1722086730 Timestamp [UCT]: 2024-07-27 13:25:30 Age [y:d:h:m:s]: 01:149:16:33:43
Block: 1074855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365530 RingCT/type: yes/0
Extra: 0194c382b791f48169eeace53b0246635f79d6dfaf416f4907a2ae888e28b6311b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53595d019d2b91e9eba0c5d6c33a1c8d04a78f5c1f5d2b5754f3375f0cbee70d 0.600000000000 1547374 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": 1074865, "vin": [ { "gen": { "height": 1074855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53595d019d2b91e9eba0c5d6c33a1c8d04a78f5c1f5d2b5754f3375f0cbee70d" } } ], "extra": [ 1, 148, 195, 130, 183, 145, 244, 129, 105, 238, 172, 229, 59, 2, 70, 99, 95, 121, 214, 223, 175, 65, 111, 73, 7, 162, 174, 136, 142, 40, 182, 49, 27, 2, 17, 0, 0, 0, 6, 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