Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12ed032f424b73fb25e584832485bdd931b7b4bc5f8ecbb4722c87273d75af1f

Tx prefix hash: c697b94ba9f192ad987b5f459be61626c2f79947eeb983938d71fe2ffd29df0f
Tx public key: 342335e7d891c822c90687bb5384669d9db6c47d3e1f029179e0c6b834c8d347
Timestamp: 1738873162 Timestamp [UCT]: 2025-02-06 20:19:22 Age [y:d:h:m:s]: 00:286:11:42:07
Block: 1213598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202508 RingCT/type: yes/0
Extra: 01342335e7d891c822c90687bb5384669d9db6c47d3e1f029179e0c6b834c8d347021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75dd36de88587a0f2c2736c55a40b068764a3b0aef79c8d2407997d9a44cc000 0.600000000000 1700377 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": 1213608, "vin": [ { "gen": { "height": 1213598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75dd36de88587a0f2c2736c55a40b068764a3b0aef79c8d2407997d9a44cc000" } } ], "extra": [ 1, 52, 35, 53, 231, 216, 145, 200, 34, 201, 6, 135, 187, 83, 132, 102, 157, 157, 182, 196, 125, 62, 31, 2, 145, 121, 224, 198, 184, 52, 200, 211, 71, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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