Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae00f7b557d8be566b145e869a6111f3ce8ccee878778f5345b44088d2581b9

Tx prefix hash: e22e88702a10f421d18eda938a6f0fd2af463894367c611537bd6d6ea48f9e1d
Tx public key: 27ca44cacbe0e9eb5e6d6f46bf2cad4579441d009f9f3e21f1a3e890743ed33f
Timestamp: 1756245435 Timestamp [UCT]: 2025-08-26 21:57:15 Age [y:d:h:m:s]: 00:119:00:52:17
Block: 1355122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85042 RingCT/type: yes/0
Extra: 0127ca44cacbe0e9eb5e6d6f46bf2cad4579441d009f9f3e21f1a3e890743ed33f0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a86b0f09980cc3594ef7c3b4f0ce1be133cf7af7e790f66c87d051946e67272 0.600000000000 1843119 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": 1355132, "vin": [ { "gen": { "height": 1355122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a86b0f09980cc3594ef7c3b4f0ce1be133cf7af7e790f66c87d051946e67272" } } ], "extra": [ 1, 39, 202, 68, 202, 203, 224, 233, 235, 94, 109, 111, 70, 191, 44, 173, 69, 121, 68, 29, 0, 159, 159, 62, 33, 241, 163, 232, 144, 116, 62, 211, 63, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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