Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50291f4726e8f337f13c88661708d7c5b65148ebf3673196f490ff96c381b283

Tx prefix hash: 9f0223f009bc80623438903f198560c3613fcc1b277f4564b3dd39f9d1b35bfe
Tx public key: af789340376ad0e3bb0df61cf8d0f82a4506a1e0e3fe00730dc430e159efc7c3
Timestamp: 1719787746 Timestamp [UCT]: 2024-06-30 22:49:06 Age [y:d:h:m:s]: 01:130:23:57:54
Block: 1055786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352164 RingCT/type: yes/0
Extra: 01af789340376ad0e3bb0df61cf8d0f82a4506a1e0e3fe00730dc430e159efc7c30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa69729f06e878f7ff2f5bdc45d65c465691f6bcfeaf9497791cbd9f61804330 0.600000000000 1526191 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": 1055796, "vin": [ { "gen": { "height": 1055786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa69729f06e878f7ff2f5bdc45d65c465691f6bcfeaf9497791cbd9f61804330" } } ], "extra": [ 1, 175, 120, 147, 64, 55, 106, 208, 227, 187, 13, 246, 28, 248, 208, 248, 42, 69, 6, 161, 224, 227, 254, 0, 115, 13, 196, 48, 225, 89, 239, 199, 195, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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