Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b1fc424cf08f6165b39a726427bfd1bc7ee6aed1dfc922a5f409fa9dce3d87

Tx prefix hash: 1a1552b7a1a105af26865e122488eb03b23a335c53d67951597281187300833a
Tx public key: 62a5804d8d0f9981a4b75cf89583efc2ce51862d5d84a5c789402ce0eaf12ec9
Timestamp: 1713952416 Timestamp [UCT]: 2024-04-24 09:53:36 Age [y:d:h:m:s]: 01:197:09:31:41
Block: 1007423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399714 RingCT/type: yes/0
Extra: 0162a5804d8d0f9981a4b75cf89583efc2ce51862d5d84a5c789402ce0eaf12ec90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdb53d6582eab503fa5c1fa77528d52673164d0714d0d6a876a0ba604ef51c4b 0.600000000000 1468755 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": 1007433, "vin": [ { "gen": { "height": 1007423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb53d6582eab503fa5c1fa77528d52673164d0714d0d6a876a0ba604ef51c4b" } } ], "extra": [ 1, 98, 165, 128, 77, 141, 15, 153, 129, 164, 183, 92, 248, 149, 131, 239, 194, 206, 81, 134, 45, 93, 132, 165, 199, 137, 64, 44, 224, 234, 241, 46, 201, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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