Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f07cf6d71c2eb20257627db1d6ef634f3ad91f0965f833574b38ed6becebdbe

Tx prefix hash: d62d148daa3fe3096303a5e68ae7c113698f4ef6b0b499e9ef92b335934d4fe9
Tx public key: 08afa9138cb6573233a4edb4825d077000ac796b8b37bb8bd5aa05ee4accc572
Timestamp: 1636688783 Timestamp [UCT]: 2021-11-12 03:46:23 Age [y:d:h:m:s]: 03:044:15:14:50
Block: 372546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810522 RingCT/type: yes/0
Extra: 0108afa9138cb6573233a4edb4825d077000ac796b8b37bb8bd5aa05ee4accc5720211000000066a2c97e6000000000000000000

1 output(s) for total of 35.776746304000 dcy

stealth address amount amount idx
00: 31f277e24d1e3cafbfd7931659d10ec144f14f1f8f572ec190e0462c1cb7ea5e 35.776746304000 754646 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": 372556, "vin": [ { "gen": { "height": 372546 } } ], "vout": [ { "amount": 35776746304, "target": { "key": "31f277e24d1e3cafbfd7931659d10ec144f14f1f8f572ec190e0462c1cb7ea5e" } } ], "extra": [ 1, 8, 175, 169, 19, 140, 182, 87, 50, 51, 164, 237, 180, 130, 93, 7, 112, 0, 172, 121, 107, 139, 55, 187, 139, 213, 170, 5, 238, 74, 204, 197, 114, 2, 17, 0, 0, 0, 6, 106, 44, 151, 230, 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