Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0948faccbc3174bf40f27282e2ee1a0898661511f20b414b7ecdb57926d1aa50

Tx prefix hash: 2b82fec96652a0f0dcd806c1854f9f36374287a118e1e258161f3296f0043b5f
Tx public key: 352319d0a136e717f898c7db6383c45ab70510575a536264b294a458b94c46c9
Timestamp: 1700904635 Timestamp [UCT]: 2023-11-25 09:30:35 Age [y:d:h:m:s]: 01:271:17:24:18
Block: 899245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453160 RingCT/type: yes/0
Extra: 01352319d0a136e717f898c7db6383c45ab70510575a536264b294a458b94c46c9021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.643321410000 dcy

stealth address amount amount idx
00: 60a0dc646f01bfce91728dc4039fdcbc07c3fbf2b593fb8bea01534bec2bc6f4 0.643321410000 1355692 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": 899255, "vin": [ { "gen": { "height": 899245 } } ], "vout": [ { "amount": 643321410, "target": { "key": "60a0dc646f01bfce91728dc4039fdcbc07c3fbf2b593fb8bea01534bec2bc6f4" } } ], "extra": [ 1, 53, 35, 25, 208, 161, 54, 231, 23, 248, 152, 199, 219, 99, 131, 196, 90, 183, 5, 16, 87, 90, 83, 98, 100, 178, 148, 164, 88, 185, 76, 70, 201, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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