Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e61510efab09b596e358b1b45a286b96f088954472903d3486090120c289cd6f

Tx prefix hash: af0d57a93758f9c42f4bf277c9c072375ea5be957a672f4cf1f3dc945ede7785
Tx public key: a658e5ef909d6162f10d4bdc2583bd49228cfce1dd82e0fb2b01b4cc4f115e37
Timestamp: 1754502725 Timestamp [UCT]: 2025-08-06 17:52:05 Age [y:d:h:m:s]: 00:060:05:07:24
Block: 1341604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42000 RingCT/type: yes/0
Extra: 01a658e5ef909d6162f10d4bdc2583bd49228cfce1dd82e0fb2b01b4cc4f115e3702110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93499104777a3ca280063f37d501acd21c3f25c7a6f8bb65a0b06f0ed936f33d 0.600000000000 1829429 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": 1341614, "vin": [ { "gen": { "height": 1341604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93499104777a3ca280063f37d501acd21c3f25c7a6f8bb65a0b06f0ed936f33d" } } ], "extra": [ 1, 166, 88, 229, 239, 144, 157, 97, 98, 241, 13, 75, 220, 37, 131, 189, 73, 34, 140, 252, 225, 221, 130, 224, 251, 43, 1, 180, 204, 79, 17, 94, 55, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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