Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c35d095b5da3c8c71b82ba4cb90f91376a920fc8c831d483578644e30fa420

Tx prefix hash: b3ebe41df83121f4e2506e67494295017b790efae026017a6d1c18af94ae9e44
Tx public key: ee1d1872260674e21fa0e4e61ee25ae2482c314ea3dd1f18fc70091ce0f21f20
Timestamp: 1723090512 Timestamp [UCT]: 2024-08-08 04:15:12 Age [y:d:h:m:s]: 00:266:08:56:09
Block: 1083177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190275 RingCT/type: yes/0
Extra: 01ee1d1872260674e21fa0e4e61ee25ae2482c314ea3dd1f18fc70091ce0f21f20021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2db3872f7de3ccf3a286d0c1d6951da6b86ee6b24ed7f1ca7455689af04089bb 0.600000000000 1557012 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": 1083187, "vin": [ { "gen": { "height": 1083177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2db3872f7de3ccf3a286d0c1d6951da6b86ee6b24ed7f1ca7455689af04089bb" } } ], "extra": [ 1, 238, 29, 24, 114, 38, 6, 116, 226, 31, 160, 228, 230, 30, 226, 90, 226, 72, 44, 49, 78, 163, 221, 31, 24, 252, 112, 9, 28, 224, 242, 31, 32, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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