Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07b2bd9aeeb2de218b7c20279175db52127eb1ac4ccf8973caf8574a0c5d04b8

Tx prefix hash: 091e03a0e18b7d8a827067040ddf28fcfc248a66e87ab575ab527535776ecc4a
Tx public key: 459063a5d2d9a0da2777167cc33db0a68e193275295bbd32e8b58fdff6507903
Timestamp: 1631612930 Timestamp [UCT]: 2021-09-14 09:48:50 Age [y:d:h:m:s]: 03:206:07:18:19
Block: 333550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 922844 RingCT/type: yes/0
Extra: 01459063a5d2d9a0da2777167cc33db0a68e193275295bbd32e8b58fdff650790302110000001336fe6557000000000000000000

1 output(s) for total of 48.173791445000 dcy

stealth address amount amount idx
00: 3266a171a79e911983d1f3f109dedfbf8b1b36af936118ebf7dcb4b823aa9348 48.173791445000 688247 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": 333560, "vin": [ { "gen": { "height": 333550 } } ], "vout": [ { "amount": 48173791445, "target": { "key": "3266a171a79e911983d1f3f109dedfbf8b1b36af936118ebf7dcb4b823aa9348" } } ], "extra": [ 1, 69, 144, 99, 165, 210, 217, 160, 218, 39, 119, 22, 124, 195, 61, 176, 166, 142, 25, 50, 117, 41, 91, 189, 50, 232, 181, 143, 223, 246, 80, 121, 3, 2, 17, 0, 0, 0, 19, 54, 254, 101, 87, 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