Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeabd89a82322508916fc68a6735152a2909045f8c5704669771dcb94ade82ff

Tx prefix hash: c4539c2e3d2d5711ca1e9801a37583ed637c4316fb3b6fa59a3cde3cdd7ae020
Tx public key: 2293ba449dc549b9179d564b535a394319c37716e267b4f3ea25d131092a0b6a
Timestamp: 1585240311 Timestamp [UCT]: 2020-03-26 16:31:51 Age [y:d:h:m:s]: 04:353:00:35:40
Block: 88057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150485 RingCT/type: yes/0
Extra: 012293ba449dc549b9179d564b535a394319c37716e267b4f3ea25d131092a0b6a0211000001f886362411000000000000000000

1 output(s) for total of 313.495551766000 dcy

stealth address amount amount idx
00: d7410121d0f7e7e64fe62648eb64260c10a616f02e0c03d248d5d9f544611798 313.495551766000 158551 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": 88067, "vin": [ { "gen": { "height": 88057 } } ], "vout": [ { "amount": 313495551766, "target": { "key": "d7410121d0f7e7e64fe62648eb64260c10a616f02e0c03d248d5d9f544611798" } } ], "extra": [ 1, 34, 147, 186, 68, 157, 197, 73, 185, 23, 157, 86, 75, 83, 90, 57, 67, 25, 195, 119, 22, 226, 103, 180, 243, 234, 37, 209, 49, 9, 42, 11, 106, 2, 17, 0, 0, 1, 248, 134, 54, 36, 17, 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