Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec1380ea3e86f7ff836c9397ab08ec62afea3274813235cbd72330883000a12

Tx prefix hash: 07e11e2b1ce57bfa25c2ba7a7214df1e4efb162a893eeaaab63a4a4a54f5ad73
Tx public key: 298fb74c1a2c0bb5c71f5f4f8c9f486ec80e3b732d7d905313f5337ef4cf66e6
Timestamp: 1734005750 Timestamp [UCT]: 2024-12-12 12:15:50 Age [y:d:h:m:s]: 00:097:11:11:20
Block: 1173587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69445 RingCT/type: yes/0
Extra: 01298fb74c1a2c0bb5c71f5f4f8c9f486ec80e3b732d7d905313f5337ef4cf66e6021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07cd7e31ea51141f1a3e283047225e09f8eecb82ad44a48dd883f6a1d55372f4 0.600000000000 1659626 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": 1173597, "vin": [ { "gen": { "height": 1173587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07cd7e31ea51141f1a3e283047225e09f8eecb82ad44a48dd883f6a1d55372f4" } } ], "extra": [ 1, 41, 143, 183, 76, 26, 44, 11, 181, 199, 31, 95, 79, 140, 159, 72, 110, 200, 14, 59, 115, 45, 125, 144, 83, 19, 245, 51, 126, 244, 207, 102, 230, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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