Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8cab0b68a4dcbff60ed60b243f4d93620d1a92b827960967d74ee080e9d0f82

Tx prefix hash: 9f479057718d7d60ff84682283a7d901a41f6099c3f54e8a914016075e89a49e
Tx public key: 3b80d73c1a09bb19649101e6c438f9f71599c76552d5b7bdb9556c6d9f79f35a
Timestamp: 1577878758 Timestamp [UCT]: 2020-01-01 11:39:18 Age [y:d:h:m:s]: 05:163:22:26:32
Block: 36308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267071 RingCT/type: yes/0
Extra: 013b80d73c1a09bb19649101e6c438f9f71599c76552d5b7bdb9556c6d9f79f35a021100000007d81c26c0000000000000000000

1 output(s) for total of 465.314678925000 dcy

stealth address amount amount idx
00: 95ed8d1c011971d6425644ef8b10e046f33b23100de2d6be18328749eb7ddad1 465.314678925000 61467 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": 36318, "vin": [ { "gen": { "height": 36308 } } ], "vout": [ { "amount": 465314678925, "target": { "key": "95ed8d1c011971d6425644ef8b10e046f33b23100de2d6be18328749eb7ddad1" } } ], "extra": [ 1, 59, 128, 215, 60, 26, 9, 187, 25, 100, 145, 1, 230, 196, 56, 249, 247, 21, 153, 199, 101, 82, 213, 183, 189, 185, 85, 108, 109, 159, 121, 243, 90, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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