Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768bbc41b8a9e754d957e3d6272478a38bbd990ef494ffd84bd7b5bff63e91f4

Tx prefix hash: ca60003e075f1ada406d087207cbd173865be0605c40373d37c33c8b4bdcd850
Tx public key: 74bcb0d23832e52b6492225188fe4d6a184522de7e6d74aa46ed7f2e814f5ec3
Timestamp: 1625847268 Timestamp [UCT]: 2021-07-09 16:14:28 Age [y:d:h:m:s]: 03:294:08:12:56
Block: 290914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 980747 RingCT/type: yes/0
Extra: 0174bcb0d23832e52b6492225188fe4d6a184522de7e6d74aa46ed7f2e814f5ec302110000000e3634f08d000000000000000000

1 output(s) for total of 66.694365648000 dcy

stealth address amount amount idx
00: 64fea76627f26ef1656a798fbc7d69545ee03cc4e42729f13a3974a0728e014b 66.694365648000 609270 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": 290924, "vin": [ { "gen": { "height": 290914 } } ], "vout": [ { "amount": 66694365648, "target": { "key": "64fea76627f26ef1656a798fbc7d69545ee03cc4e42729f13a3974a0728e014b" } } ], "extra": [ 1, 116, 188, 176, 210, 56, 50, 229, 43, 100, 146, 34, 81, 136, 254, 77, 106, 24, 69, 34, 222, 126, 109, 116, 170, 70, 237, 127, 46, 129, 79, 94, 195, 2, 17, 0, 0, 0, 14, 54, 52, 240, 141, 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