Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cad1c0af65461c55be5429b654d932befd24bf5a6e436f72366714828d9537e

Tx prefix hash: c2b8ded04956a878da864c9411f210c894fb88f5e5658982c58c0f4522a79824
Tx public key: eae199896b46aeed771d8e4b160eb4f86c84c0cd352a78a9a0ac097bd1eb7e3a
Timestamp: 1649820848 Timestamp [UCT]: 2022-04-13 03:34:08 Age [y:d:h:m:s]: 02:336:12:03:09
Block: 479063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760154 RingCT/type: yes/0
Extra: 01eae199896b46aeed771d8e4b160eb4f86c84c0cd352a78a9a0ac097bd1eb7e3a0211000000282e6b1fd5000000000000000000

1 output(s) for total of 15.873242410000 dcy

stealth address amount amount idx
00: f183d0d1c7fcf54c9db9c911c50ccbe8b385e9f76d5886eb5e334058a0a4cb41 15.873242410000 899890 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": 479073, "vin": [ { "gen": { "height": 479063 } } ], "vout": [ { "amount": 15873242410, "target": { "key": "f183d0d1c7fcf54c9db9c911c50ccbe8b385e9f76d5886eb5e334058a0a4cb41" } } ], "extra": [ 1, 234, 225, 153, 137, 107, 70, 174, 237, 119, 29, 142, 75, 22, 14, 180, 248, 108, 132, 192, 205, 53, 42, 120, 169, 160, 172, 9, 123, 209, 235, 126, 58, 2, 17, 0, 0, 0, 40, 46, 107, 31, 213, 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