Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a007989b74bdf36fef1ce2a19765de0d33b92afef71c0743b5a0b850e5751dc

Tx prefix hash: c713228ca8786434ec42836df95b0a38c7796a3c978f9aa8f72330a2e1b1303a
Tx public key: a22a292c57887304cddaecb44d5dc6e33e718094b7b16c92badbf71e6563c5cd
Timestamp: 1733959620 Timestamp [UCT]: 2024-12-11 23:27:00 Age [y:d:h:m:s]: 00:106:17:48:24
Block: 1173202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76059 RingCT/type: yes/0
Extra: 01a22a292c57887304cddaecb44d5dc6e33e718094b7b16c92badbf71e6563c5cd0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ee4db82f55835bd8a3c2e5c55aab57a45624908744159a1a6c04f0886e3fa18 0.600000000000 1659197 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": 1173212, "vin": [ { "gen": { "height": 1173202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ee4db82f55835bd8a3c2e5c55aab57a45624908744159a1a6c04f0886e3fa18" } } ], "extra": [ 1, 162, 42, 41, 44, 87, 136, 115, 4, 205, 218, 236, 180, 77, 93, 198, 227, 62, 113, 128, 148, 183, 177, 108, 146, 186, 219, 247, 30, 101, 99, 197, 205, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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