Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d2801712a2e641dfaaeb04817ccbb93b029769fdb96b4b2630cc4939914b21

Tx prefix hash: c261caeeb09f14d5ea0ce30b5d06e33e706add8fb66740d07cf1366c3725992d
Tx public key: ef0d2ef9d15146cc13974d4e3728944c9fb3f9a5c13df2641fbd660975a667e9
Timestamp: 1748275236 Timestamp [UCT]: 2025-05-26 16:00:36 Age [y:d:h:m:s]: 00:171:12:45:22
Block: 1291432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120280 RingCT/type: yes/0
Extra: 01ef0d2ef9d15146cc13974d4e3728944c9fb3f9a5c13df2641fbd660975a667e90211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e9eaa5dcea7d93acaf5b4a9ff03dbede9da998dcfbe3152a9f9e0619e445397 0.600000000000 1778903 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": 1291442, "vin": [ { "gen": { "height": 1291432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e9eaa5dcea7d93acaf5b4a9ff03dbede9da998dcfbe3152a9f9e0619e445397" } } ], "extra": [ 1, 239, 13, 46, 249, 209, 81, 70, 204, 19, 151, 77, 78, 55, 40, 148, 76, 159, 179, 249, 165, 193, 61, 242, 100, 31, 189, 102, 9, 117, 166, 103, 233, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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