Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d51701cc4f2fcc3b85e4bf82350e0a07fb37b0ac0da23e85603e7033240ad84

Tx prefix hash: 539d9212bc0fc12c2fceece6ed6049700c699adfcd98f3dfc1cd9ad9070a9261
Tx public key: e9561e192d398f891c35cbaa0beef790f8a37c81cfc54d40a34e5565daccd008
Timestamp: 1718623777 Timestamp [UCT]: 2024-06-17 11:29:37 Age [y:d:h:m:s]: 00:296:23:19:57
Block: 1046151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212217 RingCT/type: yes/0
Extra: 01e9561e192d398f891c35cbaa0beef790f8a37c81cfc54d40a34e5565daccd0080211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f0ee78942cd6cb7b2c76d8260dd2f0fb1e78e221f68f352942db4ae8ca6c7b 0.600000000000 1515930 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": 1046161, "vin": [ { "gen": { "height": 1046151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f0ee78942cd6cb7b2c76d8260dd2f0fb1e78e221f68f352942db4ae8ca6c7b" } } ], "extra": [ 1, 233, 86, 30, 25, 45, 57, 143, 137, 28, 53, 203, 170, 11, 238, 247, 144, 248, 163, 124, 129, 207, 197, 77, 64, 163, 78, 85, 101, 218, 204, 208, 8, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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