Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17d3ee795dde4d0cb38188701685e82382f535ca23ab2177ac8d9ef935ff8b61

Tx prefix hash: 67947633af69db9f97277ef93be0d6a8f81af4fec75ae3cbd48c2653dd8cea1f
Tx public key: ef23652fb04dc33852147649ecdcbc5df020881b3ac0224a6c2344d07225f269
Timestamp: 1694965127 Timestamp [UCT]: 2023-09-17 15:38:47 Age [y:d:h:m:s]: 01:212:06:54:04
Block: 850197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412805 RingCT/type: yes/0
Extra: 01ef23652fb04dc33852147649ecdcbc5df020881b3ac0224a6c2344d07225f26902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.935286061000 dcy

stealth address amount amount idx
00: 4194f8ee1ad644a1ba8fd34e5bff5c0d11c0a354d5d2b71bf91799b92b6bff45 0.935286061000 1303905 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": 850207, "vin": [ { "gen": { "height": 850197 } } ], "vout": [ { "amount": 935286061, "target": { "key": "4194f8ee1ad644a1ba8fd34e5bff5c0d11c0a354d5d2b71bf91799b92b6bff45" } } ], "extra": [ 1, 239, 35, 101, 47, 176, 77, 195, 56, 82, 20, 118, 73, 236, 220, 188, 93, 240, 32, 136, 27, 58, 192, 34, 74, 108, 35, 68, 208, 114, 37, 242, 105, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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