Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bebb4c0f493334400d1933b3af1ab57b1279c5431f4979e7123b556454cc883c

Tx prefix hash: b0b97126672e40aa7dd987ae6d90b62e137801f88113bcee4b8278022a5c00f3
Tx public key: 7e7d69c82867c08ed550a49d59759569e4dcf84759c0d5d2cfb402bff7b7490a
Timestamp: 1739860091 Timestamp [UCT]: 2025-02-18 06:28:11 Age [y:d:h:m:s]: 00:255:18:24:22
Block: 1221727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180571 RingCT/type: yes/0
Extra: 017e7d69c82867c08ed550a49d59759569e4dcf84759c0d5d2cfb402bff7b7490a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9b3a5867e6c198cd091c8a6c9a91576d141f49db650e11941427eac45f58f4 0.600000000000 1708574 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": 1221737, "vin": [ { "gen": { "height": 1221727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9b3a5867e6c198cd091c8a6c9a91576d141f49db650e11941427eac45f58f4" } } ], "extra": [ 1, 126, 125, 105, 200, 40, 103, 192, 142, 213, 80, 164, 157, 89, 117, 149, 105, 228, 220, 248, 71, 89, 192, 213, 210, 207, 180, 2, 191, 247, 183, 73, 10, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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