Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a821d1c3f722ce30b1d9059f653efa8621c365a67a8fc6b366e12de566ff32fb

Tx prefix hash: f3e99d95bc8ab99cce8c0e1eea3262620cb433b47705d11c6cc80ad319405768
Tx public key: 8b7f8421b4f4439610ff442bbf9b17781da9bf404f1d20e37eaf9972f8a183f8
Timestamp: 1704121959 Timestamp [UCT]: 2024-01-01 15:12:39 Age [y:d:h:m:s]: 01:098:14:31:46
Block: 925907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331587 RingCT/type: yes/0
Extra: 018b7f8421b4f4439610ff442bbf9b17781da9bf404f1d20e37eaf9972f8a183f80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a0eccc0856e534064e5c6b7d6404c500021f6d11c132f09f9ea524fa6df3828 0.600000000000 1383677 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": 925917, "vin": [ { "gen": { "height": 925907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a0eccc0856e534064e5c6b7d6404c500021f6d11c132f09f9ea524fa6df3828" } } ], "extra": [ 1, 139, 127, 132, 33, 180, 244, 67, 150, 16, 255, 68, 43, 191, 155, 23, 120, 29, 169, 191, 64, 79, 29, 32, 227, 126, 175, 153, 114, 248, 161, 131, 248, 2, 17, 0, 0, 0, 1, 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