Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8fafd3eca6f12f950cf55e2a1ee196ee49597f0017c88c0049b5ddbcf65a0a4

Tx prefix hash: 724d47844087446da33e66d28f05114942fa7535f2e768116161ace55126eaa2
Tx public key: 4da43b918ba8f5876fa7c6e7114aa31a99ce22ec9eab5ca0acbc339b90e5dd8c
Timestamp: 1649645022 Timestamp [UCT]: 2022-04-11 02:43:42 Age [y:d:h:m:s]: 03:204:18:10:52
Block: 477682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 924496 RingCT/type: yes/0
Extra: 014da43b918ba8f5876fa7c6e7114aa31a99ce22ec9eab5ca0acbc339b90e5dd8c021100000010c9067537000000000000000000

1 output(s) for total of 16.041370771000 dcy

stealth address amount amount idx
00: 89b4dc1bdcff959fe1f391353f8c14791fb5b15b15ed6ad2b299030f3fe016af 16.041370771000 898361 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": 477692, "vin": [ { "gen": { "height": 477682 } } ], "vout": [ { "amount": 16041370771, "target": { "key": "89b4dc1bdcff959fe1f391353f8c14791fb5b15b15ed6ad2b299030f3fe016af" } } ], "extra": [ 1, 77, 164, 59, 145, 139, 168, 245, 135, 111, 167, 198, 231, 17, 74, 163, 26, 153, 206, 34, 236, 158, 171, 92, 160, 172, 188, 51, 155, 144, 229, 221, 140, 2, 17, 0, 0, 0, 16, 201, 6, 117, 55, 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