Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5708ca3ea80f2c1b04ac0ec0d8c5e562682d191f662e6e68ba45b5964a5db08e

Tx prefix hash: 0e51e012ca146c6f0c9309c014f8ebaf403cad5ced3ddcc89e23ced290c85048
Tx public key: 50f12913782bcdecbd4a2f937b65e904f9395ae8c49db44c47a81b37cfad4af8
Timestamp: 1608149955 Timestamp [UCT]: 2020-12-16 20:19:15 Age [y:d:h:m:s]: 04:009:10:31:34
Block: 163371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1019336 RingCT/type: yes/0
Extra: 0150f12913782bcdecbd4a2f937b65e904f9395ae8c49db44c47a81b37cfad4af80211000003e94ea414e5000000000000000000

1 output(s) for total of 176.610227161000 dcy

stealth address amount amount idx
00: 5f6cf7fdaeba71bba28953532340e687a946e378a2996ceae9ae43b093c1f199 176.610227161000 293070 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": 163381, "vin": [ { "gen": { "height": 163371 } } ], "vout": [ { "amount": 176610227161, "target": { "key": "5f6cf7fdaeba71bba28953532340e687a946e378a2996ceae9ae43b093c1f199" } } ], "extra": [ 1, 80, 241, 41, 19, 120, 43, 205, 236, 189, 74, 47, 147, 123, 101, 233, 4, 249, 57, 90, 232, 196, 157, 180, 76, 71, 168, 27, 55, 207, 173, 74, 248, 2, 17, 0, 0, 3, 233, 78, 164, 20, 229, 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