Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3817e7c9a1c4868cd4e7fded8fac283691a8b7e9b459c987ba50019d53bdcb5

Tx prefix hash: ec3451a50a5b9217f68997a73d8250bcbd42b24a4b45b2bf0153fb7f26b1dd65
Tx public key: 5e138fdeffd7aabdafd608fb50527aab19cd2d50a158ed7c5c82a9bf49445ec1
Timestamp: 1751657942 Timestamp [UCT]: 2025-07-04 19:39:02 Age [y:d:h:m:s]: 00:130:15:31:44
Block: 1318798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91675 RingCT/type: yes/0
Extra: 015e138fdeffd7aabdafd608fb50527aab19cd2d50a158ed7c5c82a9bf49445ec102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfd3ad9fd63d1a3332df736880b3ec61bba3aee7a391140cd1df5a1be7a422f7 0.600000000000 1806485 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": 1318808, "vin": [ { "gen": { "height": 1318798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfd3ad9fd63d1a3332df736880b3ec61bba3aee7a391140cd1df5a1be7a422f7" } } ], "extra": [ 1, 94, 19, 143, 222, 255, 215, 170, 189, 175, 214, 8, 251, 80, 82, 122, 171, 25, 205, 45, 80, 161, 88, 237, 124, 92, 130, 169, 191, 73, 68, 94, 193, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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