Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b31279630a501428d44c4bb7dfa058dc55b266ab0e730c5a7e5bbda026e8ffdc

Tx prefix hash: d0db6f5bc9b176df34f5fce1d9e4266f92cb195ca7ee0a050a4ba02c2876fff9
Tx public key: d1eb98b1f10f56f87a8429945af56c7b1ac9a991096e3831e5be946a0d4fd664
Timestamp: 1722813771 Timestamp [UCT]: 2024-08-04 23:22:51 Age [y:d:h:m:s]: 00:282:17:31:50
Block: 1080888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201988 RingCT/type: yes/0
Extra: 01d1eb98b1f10f56f87a8429945af56c7b1ac9a991096e3831e5be946a0d4fd664021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a110edceed95c09c438dfc90ca4454f1d6b2fa4419e06c9b2e67e78b6c88fcf3 0.600000000000 1554419 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": 1080898, "vin": [ { "gen": { "height": 1080888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a110edceed95c09c438dfc90ca4454f1d6b2fa4419e06c9b2e67e78b6c88fcf3" } } ], "extra": [ 1, 209, 235, 152, 177, 241, 15, 86, 248, 122, 132, 41, 148, 90, 245, 108, 123, 26, 201, 169, 145, 9, 110, 56, 49, 229, 190, 148, 106, 13, 79, 214, 100, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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