Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eb429bcf2e9b4d0fd843877ce9748f44095918a5c11cea30434a8e564de6827

Tx prefix hash: 14ec81350e4bfbca0b7a17331f0cc76c4a0437a002cea0ae4c12937fb595f17e
Tx public key: 8ca306e8e5431e973d010a58a5f907d4b24b7546b1d6ce79ca53405a0e17ead0
Timestamp: 1663720230 Timestamp [UCT]: 2022-09-21 00:30:30 Age [y:d:h:m:s]: 02:098:11:20:17
Block: 592293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591980 RingCT/type: yes/0
Extra: 018ca306e8e5431e973d010a58a5f907d4b24b7546b1d6ce79ca53405a0e17ead0021100000004faf35c9c000000000000000000

1 output(s) for total of 6.690945456000 dcy

stealth address amount amount idx
00: 9dc94575fe79b6a5972b21a941006b65febb79bd0a4ed453cb11d9e6a6eb16c4 6.690945456000 1026940 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": 592303, "vin": [ { "gen": { "height": 592293 } } ], "vout": [ { "amount": 6690945456, "target": { "key": "9dc94575fe79b6a5972b21a941006b65febb79bd0a4ed453cb11d9e6a6eb16c4" } } ], "extra": [ 1, 140, 163, 6, 232, 229, 67, 30, 151, 61, 1, 10, 88, 165, 249, 7, 212, 178, 75, 117, 70, 177, 214, 206, 121, 202, 83, 64, 90, 14, 23, 234, 208, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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