Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 764ff408cdc9b5cf1fdcd02694eb35a71ae1be2c5c0fc9db4d013e2445e79cb4

Tx prefix hash: 06c70b56e32a274eed06f58aa443b1fc5d6b85260184747586ddf2ba49342765
Tx public key: 15c990a121349abd196f3e7deb316a72064c39f0d67f9b67e094be4c91f7bfcb
Timestamp: 1750246745 Timestamp [UCT]: 2025-06-18 11:39:05 Age [y:d:h:m:s]: 00:148:20:00:38
Block: 1307629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104180 RingCT/type: yes/0
Extra: 0115c990a121349abd196f3e7deb316a72064c39f0d67f9b67e094be4c91f7bfcb02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b367c619d87c53e6afd3251d6fd4ebc29704d5e8e947abde65a6f62ce63748dd 0.600000000000 1795240 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": 1307639, "vin": [ { "gen": { "height": 1307629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b367c619d87c53e6afd3251d6fd4ebc29704d5e8e947abde65a6f62ce63748dd" } } ], "extra": [ 1, 21, 201, 144, 161, 33, 52, 154, 189, 25, 111, 62, 125, 235, 49, 106, 114, 6, 76, 57, 240, 214, 127, 155, 103, 224, 148, 190, 76, 145, 247, 191, 203, 2, 17, 0, 0, 0, 1, 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