Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8efc5b582cc15b0ab23143a5ef1e212f8634a90c551b4d29cba97d3c415b578

Tx prefix hash: 07eb44d7847764efa60c3d090d5d7b7097420a8385e3b36fee85a30d80ff853c
Tx public key: 110ee1084184f4031c78e4f87e3b14bf16407ec00ebc816d5c4819652b760bf6
Timestamp: 1612881464 Timestamp [UCT]: 2021-02-09 14:37:44 Age [y:d:h:m:s]: 04:093:13:44:03
Block: 195278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086501 RingCT/type: yes/0
Extra: 01110ee1084184f4031c78e4f87e3b14bf16407ec00ebc816d5c4819652b760bf60211000000ba4ea414e5000000000000000000

1 output(s) for total of 138.345026871000 dcy

stealth address amount amount idx
00: 792d9274b152d57a3a76af47057ca4d93345bbefb65c4a750ef6d55fd37c8e7b 138.345026871000 397340 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": 195288, "vin": [ { "gen": { "height": 195278 } } ], "vout": [ { "amount": 138345026871, "target": { "key": "792d9274b152d57a3a76af47057ca4d93345bbefb65c4a750ef6d55fd37c8e7b" } } ], "extra": [ 1, 17, 14, 225, 8, 65, 132, 244, 3, 28, 120, 228, 248, 126, 59, 20, 191, 22, 64, 126, 192, 14, 188, 129, 109, 92, 72, 25, 101, 43, 118, 11, 246, 2, 17, 0, 0, 0, 186, 78, 164, 20, 229, 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