Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166eee608f775b6f7280108eded9f963f14cac8c6f1b6dda8adc84c577a4d2df

Tx prefix hash: 87c17724e9f96e87863ed76b92f506c70f0961265f3974ed4e4d13693f0c8a8d
Tx public key: fc1632b536ac640fbcf66eeab3888a3ae99d331d946c9596daf2fb51ff8cd4a0
Timestamp: 1724560910 Timestamp [UCT]: 2024-08-25 04:41:50 Age [y:d:h:m:s]: 00:091:02:15:27
Block: 1095393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65125 RingCT/type: yes/0
Extra: 01fc1632b536ac640fbcf66eeab3888a3ae99d331d946c9596daf2fb51ff8cd4a0021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d22a14c38798659cd9922ddbac60c46ff0b8783d5879faf1a4c1b5880b3ab9 0.600000000000 1570562 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": 1095403, "vin": [ { "gen": { "height": 1095393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d22a14c38798659cd9922ddbac60c46ff0b8783d5879faf1a4c1b5880b3ab9" } } ], "extra": [ 1, 252, 22, 50, 181, 54, 172, 100, 15, 188, 246, 110, 234, 179, 136, 138, 58, 233, 157, 51, 29, 148, 108, 149, 150, 218, 242, 251, 81, 255, 140, 212, 160, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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