Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff445605b93fde444075a1e6ca8121f556e25db055400e287f3f94aa0f3734c

Tx prefix hash: 9ff72ee2fa4b19ebaf22ae9649a5733dec8bffed4e18133269142f0d7a2f711a
Tx public key: 7ff1a29a7a03e608dd8e99656184a1c0e02dfffb9c7f4b7ef03e7a2f5fc1d806
Timestamp: 1712633759 Timestamp [UCT]: 2024-04-09 03:35:59 Age [y:d:h:m:s]: 01:000:16:49:30
Block: 996460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261467 RingCT/type: yes/0
Extra: 017ff1a29a7a03e608dd8e99656184a1c0e02dfffb9c7f4b7ef03e7a2f5fc1d80602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e1c8564bd022da5968ac162a6cd2b529d776af42aef70ae8fdbf9707385564a 0.600000000000 1456878 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": 996470, "vin": [ { "gen": { "height": 996460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e1c8564bd022da5968ac162a6cd2b529d776af42aef70ae8fdbf9707385564a" } } ], "extra": [ 1, 127, 241, 162, 154, 122, 3, 230, 8, 221, 142, 153, 101, 97, 132, 161, 192, 224, 45, 255, 251, 156, 127, 75, 126, 240, 62, 122, 47, 95, 193, 216, 6, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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