Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4008dbeab028155d508d96524342b19ec9d14afb8e4bbf978f840c264a5068f7

Tx prefix hash: 7acd41cea0cccc5651a3441e9e4a98c1191f918d79a2283ea2810f3f9e0c3778
Tx public key: abd958f5b855b2fe08c0611c558afd1969d8ba29b7e8da89e78fbf2ab9abd25b
Timestamp: 1574387902 Timestamp [UCT]: 2019-11-22 01:58:22 Age [y:d:h:m:s]: 05:190:15:53:22
Block: 14100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1279538 RingCT/type: yes/0
Extra: 01abd958f5b855b2fe08c0611c558afd1969d8ba29b7e8da89e78fbf2ab9abd25b02110000000166a80d00000000000000000000

1 output(s) for total of 551.165128199000 dcy

stealth address amount amount idx
00: b1458bbdd63613c251058b089a94cd277677b9ce743f0b7072bbead651321e61 551.165128199000 17452 of 0

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": 14110, "vin": [ { "gen": { "height": 14100 } } ], "vout": [ { "amount": 551165128199, "target": { "key": "b1458bbdd63613c251058b089a94cd277677b9ce743f0b7072bbead651321e61" } } ], "extra": [ 1, 171, 217, 88, 245, 184, 85, 178, 254, 8, 192, 97, 28, 85, 138, 253, 25, 105, 216, 186, 41, 183, 232, 218, 137, 231, 143, 191, 42, 185, 171, 210, 91, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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