Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d1a2caa28803d10052f5794507dc9546f9fd24327edd36d52980509aa6f567

Tx prefix hash: 0c6cdb29718257cd5fa6e505bcbb3bd9e725b8f14078bf6fc855bd78fd8ec44f
Tx public key: c161f8e8c344c590cecbd6df7ac3ebc4754e8290c70c8db5b2648d514bd2a180
Timestamp: 1704642643 Timestamp [UCT]: 2024-01-07 15:50:43 Age [y:d:h:m:s]: 01:306:13:46:49
Block: 930218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477942 RingCT/type: yes/0
Extra: 01c161f8e8c344c590cecbd6df7ac3ebc4754e8290c70c8db5b2648d514bd2a18002110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa467f8fbcf1f9948671ea68bdae0faeacd51d5197fa94ef80cb5fbbeb092eb 0.600000000000 1388100 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": 930228, "vin": [ { "gen": { "height": 930218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa467f8fbcf1f9948671ea68bdae0faeacd51d5197fa94ef80cb5fbbeb092eb" } } ], "extra": [ 1, 193, 97, 248, 232, 195, 68, 197, 144, 206, 203, 214, 223, 122, 195, 235, 196, 117, 78, 130, 144, 199, 12, 141, 181, 178, 100, 141, 81, 75, 210, 161, 128, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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